Skip to content

API reference

Read and act on your users’ mailboxes through one API: connect a mailbox, then query its messages and threads, act on messages and receive webhooks.

Preview. The API is under active development. Endpoints and schemas may still change without a version bump.

Authentication. Every /v1/* request carries Authorization: Bearer <credential>. The credential is either an Application API key (icnx_…, created in the dashboard, server-side only) or a grant token (icnxg_…, minted with POST /v1/grants/{id}/token, scoped to one mailbox).

Errors. Every error response has the shape { "error": { "code": "…", "message": "…" } }. Branch on code, not on message. A 429 rate_limited comes with a Retry-After header.

OpenAPI spec (JSON)

Information

  • OpenAPI version: 3.1.0

An application API key, icnx_…. Created in the dashboard with the scopes the application needs. Server-side only: never ship it to a browser or an app.

Security scheme type: http

A grant token, icnxg_…, minted with POST /v1/grants/{id}/token. Valid for 5 minutes and confined to one end user’s mailbox. It carries only the mail scopes (read:messages, modify:messages, delete:messages, report:spam) its API key holds. In a Whitelabel application, mail is readable only with a grant token: an API key gets 403 grant_token_required.

Security scheme type: http