edge-cache

Dangerously delete by source image

Changed on

Marks a source image as deleted, causing cache entries associated with that source image to be revalidated in the foreground on the next request. Use this method with caution because one source image can be associated with many paths and deleting the cache can cause many concurrent requests to the origin leading to cache stampede problem. This method is for advanced use cases and is not recommended; prefer using invalidateBySrcImage instead.

post/v1/edge-cache/dangerously-delete-by-src-images

Request

  • Base URL: https://api.vercel.com
  • URL: https://api.vercel.com/v1/edge-cache/dangerously-delete-by-src-images
  • Auth: HTTP bearer

Query parameters

projectIdOrNamestring required
teamIdstring
Example:team_1a2b3c4d5e6f7g8h9i0j1k2l

The Team identifier to perform the request on behalf of.

slugstring
Example:my-team-url-slug

The Team slug to perform the request on behalf of.

Request body

revalidationDeadlineSecondsinteger
srcImagesstring[] required

Changes

  • 41b1e17a4fe8Revision changes
    • breaking

      the request property type changed from number to integer

    • warning

      the request property's max was set to 31536000.00

  • 2ae10ee9d21cRevision changes
    • info

      added the non-success response with the status