/v1/events{
"subject_kind": "Deal",
"subject_id": "dl_9f2…",
"verb": "updated",
"payload": {
"stage": "negotiation",
"amount": 184000
}
}INTEGRATIONS · API
Every endpoint returns the same envelope — typed, versioned, and streamed over SSE so your UI paints as the answer forms. Watch it below.
INTEGRATIONS · HTTP API
Every endpoint returns the same envelope — typed, versioned, and streamed token-by-token so your UI can paint as the answer forms. Hover any key to see what it is.
/v1/events{
"subject_kind": "Deal",
"subject_id": "dl_9f2…",
"verb": "updated",
"payload": {
"stage": "negotiation",
"amount": 184000
}
}
Hover any "key" in the response to read what it represents. In production the stream is Server-Sent Events; the shape is identical.
API · LIFE OF A REQUEST
A request is authenticated, resolved to a tenant, typed against the graph, then streamed back. Every step is traced and stamped into the audit log.
HTTPS · HTTP/2
bearer · scope
policy engine
schema diff
SSE · tokens
immutable
INTEGRATIONS · API ENVELOPES
Common shape every inbound HTTP request decodes into.
Common shape every outbound HTTP response encodes to.
PLATFORM · CLOSE THE LOOP
Versioned, typed, streamed. Our reference spec is open. Our SDKs are thin. Our webhooks echo the exact same envelope.