mailboxes:read)
Request
Response
array
Every mailbox the organization owns, sorted by address.
Both non-active and Private mailboxes are listed. Filtering them out would
be worse than including them: an integration would report a mailbox as missing
when it exists and is simply unreadable, or not ready yet.
mode and status
tell you which endpoints will accept it.Aliases
mailboxes:read)
Addresses your organization owns that are not mailboxes in their own right.
Mail to an alias is delivered into the mailbox behind it, and you can
send as one.
owner is the mailbox the alias delivers into — and the one that files the
Sent copy and carries the sending limits when you send as the alias. An
integration reasoning about either has to know which mailbox is really behind
the address.
Only aliases pointing at a usable Smart mailbox are listed. An alias whose
target is Private or suspended is left out rather than listed and then refused
everywhere — it is not a usable sending identity, and an address that exists in
one endpoint and fails in every other is worse than one that is absent.Aliases are read-only here. Creating one reserves a name on a domain
permanently and interacts with role addresses and catch-all, which is a
considered decision rather than an API call — it stays in the dashboard.
Errors
A key with no permissions at all — possible only for keys created before
permissions existed — authenticates and then fails here with
forbidden. The
key list in Settings → API keys marks those; revoke and recreate them.
See Errors for the full response shape.