mailboxes.clearRetention
Clear retention window.
Clears this mailbox's OWN retention window. The account default, if any, then applies — the response says which window is now in force, which is why this answers the GET view rather than a bare deleted flag. Nothing already in the trash tier is restored by this: restore messages explicitly.
openemail.mailboxes.clearRetention(
mailboxId: string,
options?: CallOptions,
): ApiPromise<Retention>It calls DELETE /mailboxes/{mailboxId}/retention: Clear retention window in the API reference.
Example
const retention = await openemail.mailboxes.clearRetention(mailboxId)Arguments
| Argument | Type | Description |
|---|---|---|
mailboxId | string | Mailbox ULID identifier. The path's {mailboxId}. |
Options
It takes no options of its own. Every call also takes signal, timeout, retry and headers, which say how that one call is sent (call options).
Answer
Awaited, it is the API's JSON, Retention. It is an ApiPromise: .withResponse() gives the same with the Response it came in, for its headers.
Errors
| Status | What it means |
|---|---|
401 | unauthorized: the bearer credential is missing, malformed, expired, or revoked. Carries a WWW-Authenticate: Bearer challenge |
403 | insufficient_scope (an app password may read this policy but not clear it) |
404 | Mailbox not found or not accessible to this principal |
503 | temporary_failure: the platform's storage could not answer just now; retry after the Retry-After window. Any operation can answer this. A write that got it may have been applied, so retry it with the same idempotency key where it takes one, or read the state back first (see Transient failures in the API description) |
A failed call rejects with a RequestError: its status, and its code, the API's error. Decide on the code: one status covers several.
Types
It names these types of the API, each on a page of its own: Retention.