POST /conversations/{id}/messages
Updated Oct 1, 20261 minute read
Reply as the team
A reply from the team's side, which is every decision replying is: it takes the thread off the AI, reopens it, pulls it back from the archive, wakes it, and marks it read. Attachments are ids from POST /uploads.
Part of Conversations.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
id | path | string | Yes | A conversation id. |
Request body
application/json, required.
| Field | Type | Required | Description |
|---|---|---|---|
body | string | Yes | |
attachments | object[] | No | |
attachments[].id | string | Yes | |
attachments[].name | string | Yes |
Responses
| Status | Description |
|---|---|
200 | The message that landed. |
400 | The request is malformed, and the message names the field. |
401 | The bearer token is missing, revoked, or expired. |
404 | Not one of yours, or not there at all. |
429 | Too many requests. Wait the seconds in Retry-After. Limits depend on the plan. See rate limits. |
200 body
| Field | Type | Required | Description |
|---|---|---|---|
messageId | string | No |
Example request
curl -X POST https://api.median.sh/v1/conversations/id/messages \
-H "Authorization: Bearer $BEARER_AUTH" \
-H "content-type: application/json" \
-d '{"body":"That plan includes unlimited seats."}'