Reset Password a email account

POST/api/v1/email-accounts/{account}/reset-password
Requires anorganization API keywith the scopemailboxes:write

Parameters

NameInTypeDescription
accountrequiredpathstringThe account identifier.

Request

POST/api/v1/email-accounts/{account}/reset-password
curl -X POST 'https://app.mailyte.com/api/v1/email-accounts/01JBT8XQ2M9WYC3K4F6R7S8T9V/reset-password' \
  -H 'Authorization: Bearer mk_live_YOUR_API_KEY'
The key names its own organization, so no X-Organization-ID header is needed.

Response

Success.

  • dataobject
    • objectstringmailbox_password
    • mailbox_idstring

      The mailbox whose password changed. Retrieve it with `GET /api/v1/email-accounts/{email_account}`.

    • passwordstring

      **Returned exactly once, in this response, and never retrievable again.** Store it before you discard the response: we keep it encrypted and no endpoint can read it back, so a lost value can only be replaced by setting another password. Populated by `POST /generate-password`, which generated it. **null from `POST /reset-password`** — there you supplied the password and already hold it; null there means "not ours to return", not "unknown".

    • changed_atstring

      When the password moved — in practice the instant of this request, because both endpoints stamp it as they write and then hand back what they just wrote. **Never null in this response**, and not nullable. The column behind it IS nullable and a mailbox whose password has never been changed holds null there, but the only way to receive this object is to change one, so that null cannot reach you here. The only place the published contract reports this, and only to the caller that just moved it — the mailbox object carries no credential timestamps, so there is no endpoint that will tell you when some other mailbox's password last changed.

Returned inside the standard envelope.

Errors

StatusWhen
401The API key is missing, unknown, revoked or expired. All four answer identically, on purpose: distinguishing them would confirm which keys exist.
403The key is valid but may not do this: it lacks the required scope, its IP allowlist does not include you, or this endpoint does not accept API keys.
404No such resource in this organization.
422The request was understood but the values were not acceptable.
429Too many requests, or the organization has spent its sending allowance. `Retry-After` says how long to wait.

Every status, with what causes it and what to do, is on the error reference.