Purging

Purging effectively removes an object from edge cache, prompting future requests that would otherwise hit that cached object to proceed to origin as a cache miss.

In practice while some types of purge do effectively delete content, others will mark the content as stale, allowing you to refresh caches more gracefully if desired. This kind of purge is called a soft purge.

Purging can also be accomplished using the web interface; see our guides to single purges, wildcard purges, surrogate key purges, and soft purges.

Endpoints

Purge a URL

PURGE*

Purge everything from a service

POST/service/service_id/purge_all

Purge by surrogate key tag

POST/service/service_id/purge/key

Purge multiple surrogate key tags (JSON)

POST/service/service_id/purge

Purge multiple surrogate key tags (JSON)

POST/service/service_id/purge

Soft-purge a URL

PURGE*

Soft-purge by surrogate key tag

POST/service/service_id/purge/key

User contributed notes

We welcome comments that add use cases, ideas, tips, and caveats. All comments will be moderated before publication. To post support questions, visit our support center and we'll find you the help you need.