---
title: "Send chat in a meeting session"
method: POST
path: "/meeting_sessions/{id}/actions/send_chat"
tags: ["Meeting Session Actions"]
---

# Send chat in a meeting session

`POST /meeting_sessions/{id}/actions/send_chat`

Sends a chat message into a meeting session.

## Path parameters

- `id` string, required

## Request body

- SendChatMeetingSessionRequest
  - `text` string, required — Chat message text to send in the meeting.

## Response `202`

The chat message was accepted and is being delivered.

- ActionAcceptedResponse
  - `data` object, required
    - `accepted` true, required

## Other responses

- `400` — Bad Request
- `401` — Unauthorized. On api.telnyx.com, authentication is enforced by the API gateway before the request reaches the Meeting service, so a missing or invalid API key returns the standard Telnyx error envelope (`{"errors": [{"code": "10009", ...}]}`) rather than the single-`error` shape below.
- `403` — The authenticated credential is not permitted to perform this operation.
- `404` — Not Found
- `409` — Conflict
- `413` — Payload Too Large
- `422` — Unprocessable Entity, including an unsupported capability
- `429` — Authentication is temporarily overloaded. Retry after the number of seconds in `Retry-After`.
- `500` — Internal Server Error
- `502` — The meeting provider rejected native chat delivery.
- `503` — A required feature or dependency is not configured or authentication is unavailable.

---

[API](https://skmtc.net/team-telnyx/apis/telnyx-api-2.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api-2/revisions/3fdc16374d70/schema)