{id} is the chat_id, not a message_id.
For group chats, create the group with a text-only POST /api/v1/chats call
first. Send media and rich links through this follow-up endpoint after the
group chat exists.
Request
Send media
Upload first, then reference theattachment_id.
Send a rich link
Therich_link part shape is the same on every Chert sender line. The rich link is rendered as its own preview bubble. If a rich preview cannot be generated, the URL may be delivered as plain text instead.
title, summary, image_url, icon_url.
Send media with a rich link
This is the recommended shape for review-request messages that include a personalized image and a previewed URL.Response
message.id is the id to pass to message-scoped actions such as
POST /api/v1/messages/{id}/react.
Follow-up limit
Until the contact replies in a chat, this route sends at most three follow-ups after the opening message. Follow-ups sent through other send routes to the same chat count too; failed sends do not. The next request returns HTTP429:
429 Too Many Requests
message.received event arrives
for this chat; after the contact’s first reply the limit no longer applies to
the chat. The response carries retryable: true and no retry_after, so on
this route treat code 1007 as the follow-up limit and stop sending to that
chat instead of backing off. A tapback from the contact does not count as a
reply.
Fields
See also
Native text styles
Text formatting addstext_decorations to one text part
on enabled preview lines. Use an existing phone-addressed iMessage direct chat
and the preview’s idempotency contract. Plain text, media, and rich-link examples
above do not automatically enable decorated messages.
