Webhooks

Refresh edge cache when content changes

Connect CMS publish events to Cachely and refresh the right API or asset cache paths automatically. Keep long edge TTLs for performance without waiting for stale content to expire.

Start for Free — No Card Required Read Webhook API Docs

Refresh after publish

Trigger API or asset cache refreshes when editors publish or update content.

Long TTLs without stale content

Use aggressive edge caching while keeping published changes moving.

API and asset refresh modes

Refresh API cache, asset cache, or both depending on what changed.

Built for CMS workflows

Works with Contentful, Prismic, Storyblok, and generic webhook events.

Rotate secrets safely

Regenerate webhook URLs when needed, then update the configured CMS endpoint.

Track refresh activity

See recent webhook status and timing so teams know automation is firing.

Content freshness flow

Keep the edge fast without making editors wait

Webhooks connect editorial events to cache refresh behavior, so publishing content and serving fast cached responses can work together.

  1. 1An editor publishes or updates content in the CMS.
  2. 2The CMS sends a webhook request to the Cachely refresh URL.
  3. 3Cachely validates the secret and refreshes the configured API or asset cache path.
  4. 4The next request can use the updated edge response without waiting for a long TTL to expire.