curl --request GET \
--url https://agenticadvertising.org/api/registry/feed/stream \
--header 'Authorization: Bearer <token>'"<string>"Registry change feed stream
Subscribe to registry feed pages over Server-Sent Events. This is a push-friendly transport for the same cursor contract as /api/registry/feed: clients still persist cursor, apply only feed events, and recover from cursor_expired by re-bootstrapping. The stream emits feed events containing a full feed page, heartbeat events while caught up, and error before closing when the cursor expires or the server cannot query the feed.
curl --request GET \
--url https://agenticadvertising.org/api/registry/feed/stream \
--header 'Authorization: Bearer <token>'"<string>"Authorizations
Bearer token in the Authorization header. Two token types are accepted:
- Organization API key (
sk_...) issued via the dashboard. Org-scoped, long-lived, for server-to-server use. - User JWT obtained via the OAuth 2.1 authorization code flow with PKCE. User-scoped, short-lived. Discover the authorization server at
/.well-known/oauth-authorization-serverand the protected-resource metadata at/.well-known/oauth-protected-resource/api.
Query Parameters
Resume after this event ID
Comma-separated event type filters with glob support (e.g. property.*)
"authorization.*,publisher.adagents_changed"
Max events per SSE feed page (default 100, max 10,000)
1 <= x <= 10000Server-side interval while caught up (default 15 seconds). Backlog pages are sent without waiting.
5 <= x <= 60Response
SSE stream. event: feed data validates as a registry feed page.
Server-Sent Events stream. feed events carry JSON matching the RegistryFeedPage schema; heartbeat events carry { generated_at, cursor }.
Was this page helpful?