Event Stream (SSE)

GET

events

curl -N https://api.usenaive.ai/v1/events \
  -H "Authorization: Bearer nv_sk_live_..." \
  -H "Accept: text/event-stream"

event: domain.updated
id: 42
data: {"id":42,"companyId":"...","type":"domain.updated","createdAt":"2026-05-08T...","payload":{"action":"dns_record_set","domainId":"..."}}

: heartbeat 1720471200

Subscribe to a company-scoped Server-Sent Events stream of live events — DNS edits, activity log, approvals, and other domain events. A : heartbeat <ts> comment is emitted every ~25s so intermediate proxies don’t idle the connection out.

curl -N https://api.usenaive.ai/v1/events \
  -H "Authorization: Bearer nv_sk_live_..." \
  -H "Accept: text/event-stream"

event: domain.updated
id: 42
data: {"id":42,"companyId":"...","type":"domain.updated","createdAt":"2026-05-08T...","payload":{"action":"dns_record_set","domainId":"..."}}

: heartbeat 1720471200

Events vs. triggers vs. webhooks

This stream is a read-only feed you observe.
Triggers wake an agent on an inbound event.
Webhooks POST an outbound signed callback to your backend.

See Events & triggers and the event router.

curl -N https://api.usenaive.ai/v1/events \
  -H "Authorization: Bearer nv_sk_live_..." \
  -H "Accept: text/event-stream"

event: domain.updated
id: 42
data: {"id":42,"companyId":"...","type":"domain.updated","createdAt":"2026-05-08T...","payload":{"action":"dns_record_set","domainId":"..."}}

: heartbeat 1720471200

​Events vs. triggers vs. webhooks

Events vs. triggers vs. webhooks