Skip to Content
API access is available to organizations with a signed BAA. Request API access →
API referenceSend a message

Send a message

POST/me/conversations/{conversationId}/messages

Sends a text message as the connected person in one of their own conversations, a team chat or a patient conversation, and marks it as read for them. Set reply_to_message_id to reply in a thread. To message a patient by patient ID or phone number, use Send a message to a patient.

Scope
messages.write
Idempotent
With Idempotency-Key

Path parameters

conversationIdUUIDRequired

ID of the conversation.

Headers

Idempotency-KeyUUIDRequired

A UUID you generate for each write. Retrying with the same key returns the original result for 24 hours. Reusing a key with a different method, path, or body returns 409.

Body parameters

A text message. Sending files through the API isn’t available yet.

bodystringRequired

Message text, up to 10,000 characters.

reply_to_message_idUUID or null

Set to reply in a thread.

Returns

Returns 201 Created with the Message object.

Errors

Failed requests return application/problem+json problem details. The errors specific to this endpoint:

StatusCodeMeaning
400invalid_requestThe request is malformed, such as invalid JSON.
401invalid_tokenThe API key or access token is missing, expired, or revoked.
403insufficient_scopeThe credential doesn’t have the scope this endpoint needs.
403oauth_requiredAPI keys can’t use this endpoint. It needs an org admin’s OAuth token.
404not_foundThe resource doesn’t exist, or isn’t visible to this credential.
409idempotency_key_reusedThe Idempotency-Key was already used with a different request.
409idempotency_request_in_progressA request with this Idempotency-Key is still running. Retry shortly.
422validation_failedA field failed validation. See field_errors.
429rate_limitedToo many requests. Retry after Retry-After seconds.
Last updated on