Withdraw AI consent entirely

DELETE/api/v1/mailbox/ai/consent

Requires amailbox token— it acts as one mailbox holder, not as the organization.

Withdraws both the assistant and training decisions and writes a 'revoked' ledger entry with its own receipt document. Idempotent: with nothing to withdraw it succeeds without writing anything.

Request

DELETE/api/v1/mailbox/ai/consent

curl -X DELETE 'https://app.mailyte.com/api/v1/mailbox/ai/consent' \
  -H 'Authorization: Bearer MAILBOX_TOKEN'

const response = await fetch('https://app.mailyte.com/api/v1/mailbox/ai/consent', {
  method: 'DELETE',
  headers: {
    Authorization: 'Bearer MAILBOX_TOKEN',
  },
});
const { data } = await response.json();

import requests
response = requests.delete(
    "https://app.mailyte.com/api/v1/mailbox/ai/consent",
    headers={"Authorization": "Bearer MAILBOX_TOKEN"},
)
data = response.json()["data"]

<?php

$response = Http::withToken('MAILBOX_TOKEN')
    ->delete('https://app.mailyte.com/api/v1/mailbox/ai/consent');

$data = $response->json('data');

require "net/http"
require "json"
uri = URI("https://app.mailyte.com/api/v1/mailbox/ai/consent")
request = Net::HTTP::Delete.new(uri)
request["Authorization"] = "Bearer MAILBOX_TOKEN"
response = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |http| http.request(request) }

The key names its own organization, so no X-Organization-ID header is needed.

Response

Successful Response

Returned inside the standard envelope.

Errors

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