Authentication
Send an API key as a bearer token. The key must carry the mail.manage permission; a key without it is refused with 403, not 404.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X POST https://api.zinndigital.com/v1/mail/mailboxes/{mailboxId}/password \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Mints a **new** password and returns it once. Always a reset, never a read: there is no column holding the old one and no path that could write one. Requires `mail.manage`.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
mailboxId (path) | Uuid | Yes | Mailbox ID (UUIDv7). |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
mailbox | Mailbox | Yes | One mailbox. Never carries a password — see `MailboxCreated`. |
password | object | Yes | The password, shown once. `null` when the backend reconciled to a mailbox that already existed and refused to rotate a live password. |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429 · 503