Skip to main content

​
Realtime events

The Platform API is poll-based today. Long-running operations return 202 Accepted with a _links poll target, and the partner drives the polling cadence. There is no partner-facing realtime event bus yet.

​
What to do today

For any asynchronous operation — Safe deployment, KYC processing, preflight, ramp session settlement — the pattern is:
  1. Receive a 202 Accepted with the resource snapshot and a _links.self poll link.
  2. Poll the linked resource until its terminal state is reached.
  3. Cadence is up to you; most operations complete in 10–30 seconds.
The API conventions page has the full 202 pattern.

​
What is not yet exposed

Sumvin runs an internal SSE bus for the Sumvin consumer app (chat sessions, workflow runs, agent todos). That bus is 1p-only and is not part of the partner API surface — it won’t appear in your integration. Sumvin also consumes inbound webhooks from KYC, Meld, and Plaid. Those are consumed internally to advance the user’s state; they are not re-emitted to partner webhooks today. A partner-facing realtime surface (SSE or webhooks) is on the roadmap but not yet available. Build against the polling model for now.

​
See also

​
Referenced from