Documentation
Inboxes
Threads, assignments, labels, search and attachments.
An inbox gives an address on a verified domain a stored conversation history. Incoming mail is grouped into threads, can be read by the dashboard or API, and can be answered from the same address. Replies can carry up to five attachments (10 MiB total), which are stored and included in the outbound MIME message. Threads support assignees, labels, search and inbound attachments. This is useful for support addresses and agents that need a mailbox rather than a one-way webhook.
# create (admin scope)
curl -X POST https://transmitly.io/v1/inboxes -H "Authorization: Bearer $TRANSMITLY_KEY" -H "Content-Type: application/json" -d '{"address":"[email protected]","name":"Support","from_name":"Ada from Support"}'
# list threads and read one
GET /v1/inboxes/{id}
GET /v1/inboxes/{id}/threads/{thread_id}
# reply inside the thread (send or admin scope)
POST /v1/inboxes/{id}/threads/{thread_id}/reply
{"text":"Thanks — see the attached log.",
"attachments":[{"filename":"log.txt","content_type":"text/plain","data":"PGJhc2U2ND4="}]}
# assign, label, archive
PATCH /v1/inboxes/{id}/threads/{thread_id}
{"assignee_id":"mem_…","labels":["billing","urgent"]}Assigning a thread to another member creates an in-app notification with a deep link to the inbox; the bell in the top bar shows unread notifications. Members can turn the assignment email copy on or off in Settings; in-app notifications are always created. A separate daily digest preference sends one summary email when unread notifications are waiting. Creating and deleting inboxes requires the admin scope. Reading conversations and replying accepts a session or API key; replies require the send scope. Every inbound message emits inbox.message.received for webhook consumers.
Need the full API surface? OpenAPI 3.1.