Match Chat
Send A Message To A Match Chat Room
Post a message to a match’s chat room as a participant.
POST
Permission Required
This endpoint requireschat.write:write on your API key. The sender is always the API key owner, derived from the key itself - it is never accepted as a body field. A free (api_free) key receives 403 error_api_feature_required; this requires an api_pro+ plan.
Access / Membership Rules
This route is participant-gated. The API key owner may only send a message in a match they participate in (a member of one of the match’s teams). The gate is re-applied inside Convex: a non-participant returns403 CHAT_ACCESS_DENIED, and a match with no chat room returns 404 CHAT_ROOM_NOT_FOUND.
The route supports the Idempotency-Key header. Supplying one makes a retried send safe - the same key and request body returns the original result rather than posting a duplicate.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
content | string | Yes | Message body (1-255 chars). |
What’s Returned
Returns an object withsuccess: true, the created messageId, and a timestamp. Mintlify renders the full schema from the spec below.
Authorizations
Send your API key as: Authorization: Bearer tb_
Path Parameters
Match ID. The caller must be a participant of this match.
Body
application/json
Sends a message to the match chat room as the API key owner.
Message body (1-255 chars).
Required string length:
1 - 255