profound-logoProfound CMS
⌘K
Admin
Theme
DocsTutorialBlogPhilosophy
DocsTutorialBlogPhilosophy

Hybrid

Collection of Pages with ComponentsTypes of ComponentsSetup server sent events (SSE) content refetchInstall Profound CMS as a proxyCEL Scripting in Template BuilderProject ScaffoldingMedia Library

Headless

Quick startSplit Screen JSON Component Builder with LLMComponent Zod Pull

REST API

REST API OverviewgetConnect your websitegetGET /routesgetGET /routegetGET /blocksgetGET /blocks/with-cel-cachegetGET /blocks/generatedgetGET /componentsgetGET /components/{name}getGET /dataset/{schema_name}getGET /content-changes (SSE)patchPATCH /dataset/{schema_name}postPOST /translationpatchPATCH /translationsgetGET /usagepostPOST /csvpatchPATCH /csv
All Systems Operational
Powered Byprofound-logo
Theme

GET /content-changes (SSE)

Server-Sent Events stream of content-change signals for a website.

A long-lived Server-Sent Events (SSE) stream of content-change events for a website. Each event tells the client to revalidate now. This replaces the tRPC subscription that timed out on serverless platforms.

Auth: API key (only required when the server sets require_schema_api_key = true).

Query parameters

ParamTypeRequiredNotes
websiteIduuidnoTarget website; falls back to Host header / config.
api_keystringnoAlternative to the x-api-key header.

Behavior

  • Content-Type: text/event-stream.
  • Keep-alive comments every 15 seconds.
  • Emits one message event per content change whose website_id matches the resolved tenant; the event data: payload is the change serialized as JSON. Changes for other websites are filtered out.
  • The connection is held open indefinitely, and no database connection is pinned for the stream's lifetime.

Example

curl -N '{CMS_API_URL}/content-changes?websiteId=<uuid>' \
  -H 'x-api-key: <key>'

-N disables curl buffering so events appear as they arrive.

Errors

  • 400 — unresolvable or invalid websiteId
  • 401 — invalid API key
  • 500 — connection pool failure
Continue Reading
Previous‹GET /dataset/{schema_name}NextPATCH /dataset/{schema_name}›