Origami Image Service

Optimise and resize images easily

Purging Images

To use these endpoints you need to set the header FT-Origami-Api-Key with your API key. If you would like an API key, please request one by emailing origami.support@ft.com and explaining what you are wanting the API key for.

GET /v2/images/purge/:uri

Finds the correct HTTP URL equivalent of the uri being requested to purge and redirects to /v2/purge/url?url=:URL-to-purge to initaite the purge request.

GET /v2/purge/url?url=:URL-to-purge&transforms

Purge the original image and all images based on the original image from Cloudinary and Fastly. The image can take up to one hour to purge from Cloudinary and up to two hours to purge from Fastly. If the transforms query parameter is also supplied in the request then all transforms of the original image will be purged from Fastly.

GET /v2/purge/key?key=:surrogate-key

Purge from Fastly all resources which are tagged with the surrogate-key. You can view the surrogate-keys by adding the header FT-Debug: true to a request. The types of surrogate-keys available are as follows:

Surrogate Key Types Description
everything

The surrogate key origami-image-service is added to every image, purging this will remove all images from Fastly. Recommended to only use this in extreme circumstances.

scheme

Each scheme has it's own surrogate key in order to remove all images requested with the scheme from Fastly.

The scheme surrogate key is the third value in the surrogate-key header.

image response type

The response type of the image is used as a surrogate key, purging this will remove all images of the same response type from Fastly.

The image type surrogate key is the second value in the surrogate-key header.

requested image

The requested image is used as a surrogate key, purging this will remove all images based on the original image from Fastly.

The requested image surrogate key is the fourth value in the surrogate-key header.