Agent Email

Email inboxes for AI agents: threads, replies, metrics.

Agent Email gives agents their own inboxes: create them, send, read threads and reply.

GET/POST/api/v1/inboxesElenca o crea una agent inbox.(scope: inbox:read|write)
GET/PATCH/DELETE/api/v1/inboxes/:idDettaglio, aggiorna o elimina una inbox.(scope: inbox:read|write)
POST/api/v1/inboxes/:id/sendInvia un'email dalla inbox.(scope: inbox:send)
POST/api/v1/inboxes/:id/draftsCrea una bozza nella inbox.(scope: inbox:write)
GET/api/v1/inboxes/:id/threadsElenca i thread della inbox.(scope: inbox:read)
GET/api/v1/inboxes/:id/threads/:threadIdDettaglio thread con messaggi.(scope: inbox:read)
POST/api/v1/inboxes/:id/threads/:threadId/replyRispondi a un thread.(scope: inbox:send)
GET/api/v1/inboxes/metricsMetriche agent email (volumi, consegna, bounce).(scope: inbox:read)

Attachments

POST /api/v1/inboxes/:id/send and POST /api/v1/inboxes/:id/threads/:threadId/reply accept the attachments field, with the same three sources as transactional sends ({ id }, { filename, content } base64, { filename, url }): see Attachments.

curl -X POST "https://sending.dev/api/v1/inboxes/<INBOX_ID>/send" \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{ "to": "[email protected]", "subject": "The quote",
        "html": "<p>The quote you asked for is attached.</p>",
        "attachments": [{ "id": "<ATTACHMENT_ID>" }] }'

Attachments sent from an inbox land in the thread next to the received ones, so the conversation stays complete in both directions.