Mailactor

Authentication & access

Understand your organization, API key, and permissions.

Every authenticated request uses the API key supplied during onboarding:

curl --fail-with-body --silent --show-error \
  https://api.mailactor.com/v1/me \
  -H "x-api-key: $MAILACTOR_API_KEY"

An organization ID alone does not grant access. Your key identifies your organization, and resource IDs must belong to it. Keep credentials on your backend or in your agent's secret store. Never put keys in URLs, browser bundles, email bodies, or logs.

Inspect what your key can do

GET /v1/me is available to every valid tenant key without an additional scope.

Response fieldWhat to check
organization.statusYour organization must be active.
organization.sendLimitsEffective per-minute and daily sending limits.
apiKey.scopesPermissions granted to this key.
apiKey.inboxIdsAny restriction to particular inboxes.
apiKey.allowedIpsExact caller IP restrictions, when configured.
apiKey.sendModeWhether the key can start new conversations or only reply.
apiKey.allowedRecipientDomainsAny restriction on recipient domains.
apiKey.expiresAtThe key's expiration.
managedStarterYour lifetime managed-domain allowance: limit, used, remaining.
platformLimitsRecipient, content-byte, inbox, domain, and webhook caps.

Permissions by task

ScopeTasks
mailbox:manageCreate and delete inboxes; delete messages.
mailbox:readList inboxes, read threads, export messages, and access permitted attachments.
mailbox:sendSend from an inbox and reply to a thread.
delivery:readInspect submission status, events, metrics, suppressions, and complaints.
delivery:sendUse the lower-level send endpoint and manage suppressions.
domain:manageRegister, inspect, and verify customer domains.
webhook:manageCreate, list, and delete webhook endpoints.
validation:useValidate email addresses.

* grants all tenant scopes, but other key restrictions still apply. A scope does not bypass recipient policy, inbox restrictions, verified-domain requirements, or traffic limits.

When to contact us

A 401 means the key cannot authenticate from this caller: check the secret, expiry, revocation, and allowed source IPs. A 403 means an authenticated action is blocked by permissions or policy.

Key issuance, rotation, revocation, permission changes, and organization policy changes currently go through the Mailactor team. Contact us with the operation and request ID; do not include your secret.

On this page