Pods

A pod groups inboxes, domains, webhooks and lists. Use one pod per customer when you build a multi-tenant product on top of this API.

curl -X POST "$BASE_URL/v0/pods" -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" -d '{"name": "Acme", "client_id": "acme"}'

curl -X POST "$BASE_URL/v0/pods/$POD_ID/inboxes" -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" -d '{"username": "acme-support"}'

Create a key with pod_id set and it can only see that pod. Scoped keys cannot create pods. Inboxes created with POST /v0/inboxes go in the organization's default pod.

A pod that still has inboxes cannot be deleted (409 pod_not_empty), and the default pod cannot be deleted at all (403 pod_protected). Deleting an empty pod also deletes the keys and list entries scoped to it. Plan limits (inbox count, domains, webhooks) apply to the organization as a whole, not per pod.

Pods can be managed in the dashboard's Pods screen (create, delete, see a pod's inboxes, domains and webhooks, create a pod-scoped key), through the API, the Python SDK and, for create, get, list and delete, the TypeScript SDK. MCP does not cover pods.