Get started
API reference
Reach Inbox Triage from your own code or agent. Two ways in, one account: a JSON REST API and an MCP server.
Base URL
REST
https://getinboxtriage.com/api
MCP (Streamable HTTP)
https://getinboxtriage.com/mcp
Two ways in
Quick start
- Create a key. Sign in and open Settings. Create an API key and copy it. It is shown once.
- Store it. Put it in an environment variable, not in chat or in code.
Shell
export INBOX_TRIAGE_KEY="itk_..."
- Make your first call. List the inboxes on the account.
Request
curl "https://getinboxtriage.com/api/inboxes" \
-H "Authorization: Bearer $INBOX_TRIAGE_KEY"const res = await fetch("https://getinboxtriage.com/api/inboxes", {
headers: {
Authorization: `Bearer ${process.env.INBOX_TRIAGE_KEY}`,
},
});
const data = await res.json();import os
import requests
res = requests.get(
"https://getinboxtriage.com/api/inboxes",
headers={"Authorization": f"Bearer {os.environ['INBOX_TRIAGE_KEY']}"},
)
print(res.json())
Next, read Authentication and the Safety rules, then pick an endpoint from the menu.
Reference
InboxesConnected mailboxes. Add, rename, and remove them, and check whether each one can sync.MessagesRead the synced copy of each inbox, and move a message to Spam.SyncPull new mail from the provider, and load older mail for one folder.DraftsWrite drafts into the mailbox. The REST API never sends.TriageThe shared triage profile, and the lease agents take before a pass that changes mail.Account and keysThe account record, API keys, and the activity log.
MCP tools and promptsEvery tool, its inputs, and an example call.
For agents
Machine-readable summaries: /llms.txt, /capabilities.json, and /pricing.json. Step-by-step playbook: Agent setup guide.
Security contact
Report a security problem to help@getinboxtriage.com. The machine-readable contact is at /.well-known/security.txt, and the policy is on the Security page.