Gmail's API gives an agent a mailbox. Sortd's API gives it a team's email operation — threads become owned, stateful work items with AI classification, assignments, customer context and a human-in-the-loop review flow, through one contract.
Who owns a conversation, what stage it's in, who's assigned — across every mailbox on the team.
Smart status, urgency, sentiment and risk as structured labels. Raw email bodies stay in Sortd.
Sales boards and deal flow alongside the email a thread came from.
Scopes, idempotency, audit, reversible actions, and drafts-for-review — agents never send.
# 1. List the teams your key can use
curl https://api.sortd.com/v2/me \
-H "Authorization: Bearer sk_live_…"
# 2. Find work on a board
curl "https://api.sortd.com/v2/tasks?board_id=brd_…" \
-H "Authorization: Bearer sk_live_…"
# 3. Create a task (idempotent)
curl -X POST https://api.sortd.com/v2/tasks \
-H "Authorization: Bearer sk_live_…" \
-H "Idempotency-Key: my-unique-key" \
-d '{"list_id":"lst_…","title":"Follow up with Acme"}'Full walkthrough in the Quickstart. Every response is { data, meta }; tolerate unknown fields.
| Surface | What it is |
|---|---|
| REST v2 | The durable contract — explicit, typed, OpenAPI 3.1. |
| MCP | Connect Sortd inside Claude / ChatGPT / Cursor. Open-source stdio server (@sortd/mcp, MIT) + hosted transport. |
| Zapier | REST-hook + polling triggers, idempotent actions, loop detection. |
| Webhooks | Stripe-style signed delivery, retries, replay, delivery log. |
| llms-full.txt | The whole contract in one file, written for models. |