Skip to main content
POST
Purge Cache
string
required
The ID of the application to purge the cache for.
array
The hostnames to purge. Optional — omit it (an empty body is fine) and every hostname the application owns is purged, which is what a plain “purge this app’s cache” wants. When you do send it, each entry must be one of the application’s own hostnames: its subdomain, already a full host (myapp.vertraweb.app — do not append the zone again), or its attached custom domain. Anything else is rejected with INVALID_HOSTNAME_FOR_APP.
array
An optional array of full URLs to purge (e.g., ["https://example.com/path1", "https://example.com/path2"]). URLs whose host is not among the hostnames being purged are dropped; if nothing is left the request fails with NO_AUTHORIZED_PATHS. If omitted, everything under each hostname is purged.

Response

A success returns 200 with { "response": null }.

Error Responses

string
The error code indicating the reason for failure. Possible values:
  • VALIDATION_ERROR: The path parameter or the body failed validation (400). The response also carries message and path.
  • UNAUTHORIZED: The request is not authenticated (401).
  • USER_NOT_FOUND: The authenticated user could not be resolved (401).
  • ACCESS_DENIED: The user does not have permission to act on the application (403).
  • INVALID_HOSTNAME_FOR_APP: One of the hostnames does not belong to the application (403).
  • APP_NOT_FOUND: The specified application does not exist (404).
  • APP_NOT_PUBLISHED: The application has no subdomain and no custom domain, so it has no edge cache to purge (400).
  • NO_AUTHORIZED_PATHS: None of the provided paths belong to the given hostnames (400).
  • INTERNAL_SERVER_ERROR: The CDN rejected the purge (500).
  • INTERNAL_SERVER_ERROR: Unexpected failure (500).
string
A descriptive message providing additional details about the error.
This route has its own budget of 10 requests per minute. See Rate Limiting.