cherami.
API referenceSaved drafts

Retrieve a draft

GET /v1/drafts/{draft_id}

Read as Markdown ↗

GET /v1/drafts/{draft_id}

Requires an API key: Authorization: Bearer YOUR_CREDENTIAL.

Returns the draft's metadata, from (the inbox's current address and sender name) and its full saved content, attachments included as base64. The content is what you saved: Cherami adds its "Sent via Cherami" line and uses the inbox's sender name at the time you send. For a submitted draft, read the sent message named by sent_message_id for what was sent and its outcome.

Parameters

ParameterLocationRequiredTypeMeaning
draft_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/drafts/DRAFT_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.

DraftDetail

{
  "id": "11111111-1111-4111-8111-111111111111",
  "inbox_id": "11111111-1111-4111-8111-111111111111",
  "state": "draft",
  "subject": "Example",
  "created_at": "2026-10-01T00:00:00.000Z",
  "updated_at": "2026-10-01T00:00:00.000Z",
  "sent_message_id": null,
  "from": {
    "address": "my-agent@cherami.to"
  },
  "content": {
    "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.

draft_unavailable: The draft request failed. Repeat a draft send with the same draft ID: it never sends twice. Repeat a creation with its original idempotency key and payload; without a key, list drafts first. Read the draft before repeating an edit. Retry a read or a deletion.

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

Content type: application/json.

Error

Schema: DraftDetail

FieldRequiredTypeMeaning and constraints
idYesstringCherami resource ID.
inbox_idYesstringCherami resource ID.
stateYes"draft" or "submitted"
subjectYesstring
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$
updated_atYesstringUTC timestamp with milliseconds. format: date-time pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d{3}Z$
sent_message_idYesstring or null
fromYesMailbox
contentYesDraftContent

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: DraftContent

FieldRequiredTypeMeaning and constraints
toYesarray of Mailbox
ccYesarray of Mailbox
bccYesarray of Mailbox
subjectYesstring
textYesstring
htmlNostring
in_reply_toNostringCherami resource ID.
labelsNoarray of string
attachmentsYesarray of StoredAttachment

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