Purge an application's edge cache
Clear every cached edge response for an application’s domains with POST /v2/apps//network/purge_cache, so the next request is served fresh.
POST
Purge an application's edge cache
string
required
The API key for your account. You can find this in your account settings.
apps:write scope.
Purging clears every cached response Cloudflare is holding for the application’s primary domain and any attached custom domain, forcing the next request for each URL to be served fresh from the application. Use it right after deploying a change to static assets or an API response that a previous request already cached, when you cannot wait for the resource’s own cache TTL to expire.
The purge itself is asynchronous: the edge provider acknowledges the request, but propagation across edge locations is not instant. On workspace-shared applications, the caller needs the maintain or admin role. To push the changed files first, see Commit Application or Upload Application.
Parameters
string
required
The ID of the application. You can find this in the URL of your application’s dashboard.
Response
string
Indicates whether the call was successful:
success if it was, error if not.Common errors
Related
- CLI:
squarecloud app network purge-cache - SDKs:
api.apps.network.purgeCache()(JavaScript),client.apps.network.purge_cache()(Python),c.Apps.Network.PurgeCache()(Go)

