Skip to main content

GetEngagementTokens generates subscription tokens for multiple engagements in a single round trip.

POST 
/api/v1/engagements/realtime/tokens

The frontend loads an inbox of N engagements and then needs one subscription token per engagement to receive realtime updates. Doing N sequential HTTP calls is slow and -- if any one fails silently -- the affected engagement stays stale until refresh. Batching makes the failure mode visible (per-engagement error in the response) and cuts latency.

Engagements the caller cannot access are omitted from subscriptions and listed in errors with reason ENGAGEMENT_NOT_FOUND or PERMISSION_DENIED. The RPC itself returns OK as long as the request is valid.

Errors (RPC-level)​

  • INVALID_ARGUMENT: No engagement IDs provided / over limit

Request​

Responses​

A successful response.