Authorization header of the upgrade request. The key needs the streams:read scope, and live keys need a plan that includes streams.
Channels
Messages
Delivery and billing
- Events arrive in
databatches of up to 100. The next batch waits until you acknowledge the previous one. If you don’t acknowledge a batch within 10 seconds, the subscription ends withack_timeout; resubscribe from your last cursor. - Every channel costs 1 credit per acknowledged event. Replays of events you already paid for are free. A key’s per-request maximum applies to each batch.
- Test keys receive a synthetic event every 2 seconds, free.
Resuming
Keep thecursor from each data message. After a reconnect, subscribe with it to continue after your last acknowledged batch. Events stay available for about 15 minutes. If what you need is older, or was lost in an ingest outage, you get a gap message naming the missing range so you can backfill over REST. You never miss events silently.
Limits
- 20 subscriptions per connection, and one live subscription per key, channel, and target.
- Connections per workspace follow your plan: Starter 5, Growth 25, Scale 50.
- Wallets on the
orderschannel at once: Starter 10, Growth 50, Scale 200. A subscription can also be refused withorders stream capacity reachedwhile server-wide capacity is full; retry later. - Workspaces that leave 5 or more batches unacknowledged within 10 minutes (including batches dropped by unsubscribing or disconnecting) can’t open new subscriptions for a few minutes.
- Messages you send can be at most 64 KiB.
Close codes
The server re-checks your key every 5 seconds, so a revoked key or an exhausted balance closes the connection promptly.

