For API-key authentication, Sending clients accept a send-capable
smx_mbx_ key or owner-approved Sending-resource smx_agent_ token. Mailbox clients accept
smx_mbx_ keys or scoped smx_agent_ tokens. Management API-key clients require
team-scoped smx_root_ keys.Requirements
- PHP 8.2 or newer.
- Composer.
- An API key or REST OAuth grant for the surface you are calling.
Install
Install the umbrella package when one application needs more than one API surface.OAuth access tokens
ClientFactory::createMailboxAPIApiWithAccessToken() accepts a bare token or a callable returning one. Every Sending, Mailbox and Management factory has a corresponding WithAccessToken method.
OAuth factories attach credentials through their HTTP client. If you build a request with a
*Request() method, send it through ClientFactory::httpClient(accessToken: $token); the request object itself has no factory OAuth header.Create a client
PHP packages expose factory methods for each generated API group.Choose a surface
Durable
smx_agent_ tokens are mailbox-compatible and include mailbox.read
and email.receive, not email.send. After owner acceptance and approval,
exchange the durable token for a one-hour Sending-resource token before sending.https://smtp.sendmux.ai/api/v1 by default. Mailbox and Management use https://app.sendmux.ai/api/v1.
Shared API behaviour
API-key factories validate key prefixes. Both credential modes configure bearer auth and add retry middleware to generated API clients.Pagination
List responses use cursor pagination withpagination.has_more and pagination.next_cursor. The core package exports Pagination::iterate() for cursor iteration when you wrap a page-fetching function.
Retries and rate limits
Surface clients useRetryMiddleware::create() by default. It retries safe methods and retry-safe POST requests that include Idempotency-Key, then honours Retry-After and X-RateLimit-Reset response headers.
Pass RetryOptions into a factory method to change attempts, local backoff, jitter, or maxElapsedMilliseconds. Server retry delays are never shortened to fit local backoff limits. If another attempt would exceed the retry budget, the client returns the last response with its retry metadata; the budget does not interrupt an in-flight request. Responses with error.retryable: false are not retried.
Idempotency and ETags
Use core header helpers when a generated operation accepts custom headers.Idempotency-Key for retry-safe mutating requests. Use If-Match and If-None-Match with single-resource endpoints that support ETags.
Errors
The core package definesSendmuxApiError. Use ErrorMapper::fromThrowable() when you need to normalise a generated exception into the Sendmux error shape.
Use the mapped error code, retryability, status, and request ID when deciding whether to retry or contact support.
Next steps
SDK overview
Choose the right package family and API surface.
Versioning and support
Check compatibility, support, and upgrade guidance.
Management API
Review the Management API contract used by
sendmux/management.API keys
Create and scope the credentials used by SDK clients.