cherami.
API referenceSending and allowance

Read a sent message

GET /v1/sent/{message_id}

Read as Markdown ↗

GET /v1/sent/{message_id}

Requires an API key: Authorization: Bearer YOUR_CREDENTIAL.

Returns a sent message's outcome (status, error_code) and, in submission, what was sent, attachments included as base64. Names are as they were at sending, not the inbox's current settings.

Parameters

ParameterLocationRequiredTypeMeaning
message_idpathYesstringCherami resource ID returned by the API.

curl example

Supply CHERAMI_API_KEY privately.

curl --silent --show-error --include --request GET \
  "https://cherami.to/v1/sent/MESSAGE_ID" \
  --header "Authorization: Bearer $CHERAMI_API_KEY"

Responses

HTTP 200

Success.

  • X-Request-ID: Identifies this request; include it when reporting a problem.

Content type: application/json.

SentDetail

{
  "id": "11111111-1111-4111-8111-111111111111",
  "inbox_id": "11111111-1111-4111-8111-111111111111",
  "created_at": "2026-10-01T00:00:00.000Z",
  "recipient_count": 0,
  "status": "unknown",
  "provider_message_id": null,
  "error_code": null,
  "thread_id": null,
  "in_reply_to": null,
  "labels": [],
  "reply_text": null,
  "submission": {
    "from": {
      "address": "my-agent@cherami.to"
    },
    "to": [],
    "cc": [],
    "bcc": [],
    "subject": "Example",
    "text": "Example",
    "attachments": []
  }
}

HTTP 401

unauthorized: Send a valid API key as Authorization: Bearer <key>. If the key stopped working, get a new one through recovery.

  • X-Request-ID: Identifies this request; include it when reporting a problem.
  • WWW-Authenticate: "Bearer"

Content type: application/json.

Error

HTTP 404

not_found: The resource does not exist or does not belong to this account. A reply or forward source must also be in the sending inbox.

  • X-Request-ID: Identifies this request; include it when reporting a problem.

Content type: application/json.

Error

HTTP 503

content_unavailable: Stored content could not be read. Retry later.

outbound_unavailable: The request failed. If it was a send, reply or forward, its outcome is unknown: repeat it with the same idempotency key and unchanged payload within 24 hours of the first request; without a key, check sent messages before sending again. Retry a read.

  • X-Request-ID: Identifies this request; include it when reporting a problem.

Content type: application/json.

Error

Schema: SentDetail

FieldRequiredTypeMeaning and constraints
idYesstringCherami resource ID.
inbox_idYesstringCherami resource ID.
created_atYesstringUTC timestamp with milliseconds. format: date-time pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d{3}Z$
recipient_countYesintegerminimum: 0
statusYes"accepted" or "rejected" or "unknown"
provider_message_idYesstring or nullMessage-ID the provider assigned when it accepted the message.
error_codeYesstring or nullReason code for a rejected or unknown outcome, such as E_RECIPIENT_SUPPRESSED or acceptance_unknown.
thread_idYesstring or null
in_reply_toYesstring or null
labelsYesarray of string
reply_textYesstring or nullNew text without quoted history. Empty: there is none. Null: it couldn't be extracted; read submission.
submissionYesSubmission

Schema: Submission

What was sent, including the Sent via Cherami line.

FieldRequiredTypeMeaning and constraints
toYesarray of Mailbox or string
ccYesarray of Mailbox or string
bccYesarray of Mailbox or string
subjectYesstring
textYesstring
htmlNostring
attachmentsYesarray of StoredAttachment
fromYesMailbox or string
headersNoobject

headers fields

FieldRequiredTypeMeaning and constraints
In-Reply-ToYesstring
ReferencesYesstring

Schema: Mailbox

FieldRequiredTypeMeaning and constraints
addressYesstringBare address such as alex@example.com: ASCII, at most 254 characters and 64 before the @. maxLength: 254
nameNostringOptional name; blank means none. At most 256 UTF-8 bytes after trimming, without control characters. x-max-utf8-bytes: 256

Unknown fields are rejected.

Schema: StoredAttachment

FieldRequiredTypeMeaning and constraints
filenameYesstringAt most 255 UTF-8 bytes, without control characters, slashes or backslashes. minLength: 1 x-max-utf8-bytes: 255
typeYesstringMIME type without parameters. maxLength: 127 pattern: ^[A-Za-z0-9!#$&^_.+-]+/[A-Za-z0-9!#$&^_.+-]+$
contentYesstringThe file's bytes as padded base64, without line breaks. contentEncoding: base64 pattern: ^[A-Za-z0-9+/]*={0,2}$
dispositionYes"attachment" or "inline"
contentIdNostringContent-ID of an inline file carried over from a forwarded message.

Schema: Error

FieldRequiredTypeMeaning and constraints
errorYesobject

error fields

FieldRequiredTypeMeaning and constraints
codeYesstringCode to handle. Handle a code you don't recognize by its HTTP status.
messageYesstringExplanation of this case; its wording can change.

Errors, limits and pagination · Download OpenAPI 3.1

On this page