Get messages from multiple chats in bulk across the agency's creators (POST batch)
Returns the most recent messages for chats grouped by creator, across the creators the authenticated user’s agency manages, in a single request.
This collapses the outer per-creator fan-out: instead of one batch call per managed creator (POST /creators/{creatorUserUuid}/chats/messages/batch), agencies send one request grouping chat UUIDs under each creator. Each creator group takes the same chatUuids, sinceMessageUuid and limit fields as the per-creator batch, so per-key behaviour is identical — just add the creator dimension.
Per-creator and per-chat errors are reported inside the 200 response body, so a single forbidden/missing creator or chat never collapses the whole request. A creator the agency does not manage is returned as { "error": "forbidden" | "not_found" } at the creator level.
isRead reflects each message’s state at read time.read:agency— Read agency information, including the agency’s team members.read:chat— Read chat conversations, messages, and chat-related data. This includes viewing chat lists and message history.
Authorizations
OAuth 2.0 access token, presented as a JWT bearer token in the Authorization header. Obtain a token via the authorization-code flow; the scopes granted to the token determine which operations it may call.
Headers
API version to use for the request
"2025-06-26"
Body
Per-creator groups of chat UUIDs (1-25 creators)
1 - 25 elementsResponse
Per-creator, per-chat messages or error. Always 200 when the request itself is valid, even if every key fails.
Map of input creator UUID to its per-chat messages, or a creator-level error (forbidden/not_found).