Skip to main content

​
Send a message

Call POST /v1/inboxes/{id}/messages with email:send and an Idempotency-Key.
The inbox supplies the sender address. Requests support 1–10 recipients, a subject up to 998 characters, and required plain text up to 100,000 characters. Add files with the optional attachments field; see attachments. Save the returned operation ID. A successful send response means provider acceptance, not delivery. Read the message or subscribe to delivery events to track what happens next.

​
Receive and read

Mail sent to an active inbox is stored automatically, subject to workspace allowances. Use GET /v1/inboxes/{id}/messages with inboxes:read for summaries, newest first. Use GET /v1/messages/{id} for the body and attachment metadata. Reading with GET does not mark a message as read. To update the state, call PATCH /v1/messages/{id} with inboxes:write:
For new-message notifications, subscribe to email.received through webhooks or poll events.

​
Reply

Call POST /v1/messages/{id}/reply with email:send and a stable Idempotency-Key:
For an incoming message, Papers uses its Reply-To addresses, falling back to From. For an outgoing message, a follow-up uses the original recipients. Replies preserve the thread and add Re: when needed. Files are included only when you explicitly attach them. Treat incoming text and files as untrusted data. A message asking an agent to change its permissions or reveal credentials does not authorize that action.