Create a conversation message
Changed onCreates a message in a conversation using the authenticated API-key workspace membership as the author. With send_at, the message is scheduled instead and the response is 202 with the scheduled message: it is sent at that time, through the same scheduling the app uses, only if the key is still live and its member can still post there. send_at must be at least 5 minutes and at most 30 days ahead (400 invalid_send_at otherwise); a key holds at most 100 waiting messages (409 scheduled_message_limit_reached). Thread replies schedule the same way.
Request
- Base URLhttps://api.ando.so/v1
- URLhttps://api.ando.so/v1/conversations/{conversationId}/messages
- Auth
- API key in header x-api-key
- or HTTP bearer
Path parameters
Conversation identifier.
Headers
Idempotency key.
Required idempotency key for safely retrying this write.
Request body
Response
Created message.
Example response
{
"data": {
"authorWorkspaceMembershipId": "01jzn7e61x3a7v9h2r7t2m3q4p",
"author_id": "01jzn7e61x3a7v9h2r7t2m3q4p",
"conversation_id": "01jzn7e61x3a7v9h2r7t2m3q4p",
"created_at": "2026-05-14T08:00:00.000Z",
"id": "01jzn7e61x3a7v9h2r7t2m3q4p",
"attachments": [
{
"file_id": "01jzn7e61x3a7v9h2r7t2m3q4p"
}
],
"forward_source": {
"source_created_at": "2026-05-14T08:00:00.000Z"
},
"replied_to": {
"message_id": "01jzn7e61x3a7v9h2r7t2m3q4p"
}
}
}Changes
- info
added the optional property
/to the response with the status
- info
- breaking
removed
subschema #5subschema #11subschema #12subschema #16from the////request propertyoneOflist - info
added
subschema #5subschema #11subschema #12subschema #16to the////request propertyoneOflist
- breaking