What this deployment's webmail can actually do

GET/api/v1/mailbox/capabilities

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

Runtime feature detection for the webmail: which optional services are configured on THIS deployment. Distinct from /api/v1/capabilities, which reports the build's edition (CE vs Pro) and cannot answer questions like 'is an AI endpoint configured', since two deployments of the same edition differ. The webmail hides any control this does not advertise.

Request

GET/api/v1/mailbox/capabilities

curl -X GET 'https://app.mailyte.com/api/v1/mailbox/capabilities' \
  -H 'Authorization: Bearer MAILBOX_TOKEN'

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

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

<?php

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

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

require "net/http"
require "json"
uri = URI("https://app.mailyte.com/api/v1/mailbox/capabilities")
request = Net::HTTP::Get.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.