mail

POST /v1/mail/mailboxes/{mailboxId}/rename

Change a mailbox's address, keeping the mail in it.

Всички крайни точки в mail

Всички документи за разработчици

Упълномощаване

Изпратете API ключ като токен за носене. Ключът трябва да притежава разрешението mail.manage; ключ без него се отхвърля с 403, а не с 404.

Този ендпойнт не изисква идентификатор на организация. Вашият ключ вече идентифицира организацията, към която принадлежи, и отговорът е ограничен до нея.

Опитайте

Заменете всичко в квадратни скоби със собствени стойности, а ключовия заместващ символ – с ключ от вашето табло за управление.

curl -X POST https://api.zinndigital.com/v1/mail/mailboxes/{mailboxId}/rename \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "local": <string> }'

Влязохте ли в профила си? API конзолата във вашето табло за управление попълва действителното идентификационно число на вашата организация и вашия собствен ключ и изпълнява заявката спрямо реалното API, за да можете да видите действителния отговор. Отворете този крайpoint в API конзолата

Детайли

Changes the local part — sales@example.com becomes hello@example.com — with every message already in the mailbox intact. ⚖️ Part of the owner's 2026-08-16 ruling that a domain owner must be able to "create the mailboxes easily and manage them in full". A POST to a sub-resource rather than a field on updateMailbox, deliberately. A rename moves where mail is delivered; a quota edit does not. Sharing a body would let a mistyped field change a customer's address as a side effect of resizing their mailbox, and would make the two indistinguishable in the audit log. ⛔ The engine reads the mailbox back from the backend and refuses if the address did not actually change, rather than trusting the backend's success response. It never falls back to create-then-delete: that would "work" on screen and silently destroy every stored message. 409 when the target address already exists on the domain; 422 for a mailbox that has not finished provisioning, and for the system_managed address the site sends from. Requires mail.manage.

Параметри

ИмеТипЗадължителноКакво представлява
mailboxId (path)UuidДаMailbox ID (UUIDv7).

Тяло на заявката

ИмеТипЗадължителноКакво представлява
localstringДаThe new part before the @. Lower-cased and trimmed by the engine.

Отговор

ИмеТипЗадължителноКакво представлява
idUuidДаUUIDv7 identifier — sortable by creation time (docs/02 §8).
addressstringДаThe full address.
localstringДаThe part before the @.
quota_mbintegerДаThis mailbox's size in MB. 0 means no cap.
used_mbintegerДаHow much of it is used, as the mail backend last reported it (#932). Refreshed by the hourly reconcile, so it is a recent figure rather than a live one.
percent_usedintegerДаHow full, 0-100. Always 0 for an uncapped mailbox — a percentage of "no limit" is meaningless, not zero-ish. Read usage_checked_at before showing it: this is also 0 for a…
usage_checked_atstringНеWhen the backend was last asked. null until the first sweep sees it.
send_enabledbooleanДа
send_suspended_atstringНеWhen we paused this mailbox's sending because most of its recent mail was permanently refused (W43-72). null = not paused.
send_suspended_reasonstringНеThe counts that decided the pause, in plain words. Empty when not paused.
receive_enabledbooleanДа
statusMailboxStatusДаOne mailbox's state.
system_managedbooleanДаWe created this mailbox when the domain was provisioned; the customer did not ask for it. It is the address the site itself sends from, so deleteMailbox and renameMailbox
created_atstringДа

Грешки, които този крайpoint може да върне

401 · 403 · 404 · 409 · 422 · 429 · 503