Skip to Content
DELETE
/api/v1/mailboxes/{mailboxId}/event-webhook

Deletes the hook: event batches stop immediately and nothing is retained. Any batch already in flight completes its retry ladder against nothing and is dropped; re-creating the hook later starts fresh (re-sync via GET /mailboxes/{mailboxId}/messages/changes rather than expecting a backlog).

Authorization

bearerAuth
headerAuthorizationBearer <token>

Two credential kinds share this scheme; GET /api/v1/auth/whoami answers which one you hold and what it reaches.

oek_… API key (minted by POST /api/v1/api-keys; shown once at mint). role: account reaches the full account surface: the directory (domains, routes, patterns, api-keys, accounts, address lists) plus every mailbox the account owns. role: system additionally reaches the operator surface, which is documented separately.

oemp_… mailbox app password (minted by POST /api/v1/identities/{identityId}/credentials). Reaches ONE mailbox: its messages, labels, threads, search, sync, send, filters and PIM collections. Directory routes refuse it with 403 insufficient_scope.

Refusal vocabulary: a missing, malformed, expired, or revoked credential answers 401 unauthorized with a WWW-Authenticate: Bearer challenge; a VALID credential outside its scope answers 403 (insufficient_scope for an app password on a directory route, system_credentials_required where only the operator may call). The public routes (health, branding, token-in-path capabilities) declare security: [].

Path Parameters

mailboxId*string

Mailbox ULID identifier

Response Body

Removed

application/json
  1. response
deleted*boolean

True if the resource was successfully deleted

Example Request
curl -X DELETE 'https://api.open.email/api/v1/mailboxes/string/event-webhook'
Example Response
{
  "deleted": true
}