Skip to main content
The Sendmux Mailbox API is for mailbox-scoped access. Use it when a client should act as a mailbox, or as one mailbox from a connected-app mailbox set, without managing team-wide resources. Team-wide mailbox provisioning stays in the Management API. High-volume provider-routed sending stays in the Sending API.

Base URL

All Mailbox API requests should be made to:

Authentication

Authenticate with a mailbox credential, REST OAuth access token, or agent access token from Sendmux. Pass it as a Bearer token in the Authorization header.
Manual mailbox credentials are scoped to one mailbox. The same credential is also accepted as the mailbox password for SMTP submission and IMAP retrieval. Connected-app tokens can be granted one or more mailboxes, and each mailbox request is limited to that granted set. Agent access tokens use the smx_agent_ prefix and are limited by their granted scopes. Root API keys are rejected on Mailbox API endpoints. OAuth access tokens are for HTTP requests; they are not SMTP or IMAP passwords.

Current endpoints

Use GET /mailbox/connection to test an integration connection without checking storage or selecting a mailbox. GET /mailbox/me keeps its existing mailbox details and storage-usage behaviour. Import the Mailbox API Postman collection when you want ready-made requests.

Response format

The Mailbox API uses the same envelope as the Management API.

Success

Error

Every response includes an X-Request-Id header matching meta.request_id. Include that value when contacting support.

Rate limiting

Mailbox API keys are rate-limited to 1800 requests per minute. Rate limit headers are included on responses:
When the limit is exceeded, the API returns 429 rate_limit_exceeded with a Retry-After header.

Conventions

  • snake_case fields in JSON request and response bodies
  • UTC ISO 8601 timestamps in RFC 3339 format: 2026-03-19T10:30:00Z
  • Opaque IDs only for mailbox, message, folder, and attachment resources
  • Cache-Control: no-store on authenticated responses
  • Weak ETag headers on single-resource GETs where supported
  • Header-based idempotency for retriable POST requests where supported

OpenAPI specification

Mailbox API endpoints are included in the app API specification: