https://api.zapmail.ai/api/v3ACTIVE.| Topic | Behaviour |
|---|---|
| Base URL | https://api.zapmail.ai/api/v3 |
| Authentication | x-auth-zapmail header with your API key on every request. See Authentication. |
| Workspace | Optional x-workspace-key header to act in a workspace other than your primary one. |
| Request bodies | JSON. Send Content-Type: application/json. |
| Success responses | Most return { "status", "message", "data" }. A few return a different body and say so on their endpoint page. |
| Error responses | { "status", "message", "errorId" }. See Errors. |
| Lists | page and limit, with defaults that vary per endpoint. See Pagination. |
| Rate limits | 5 requests per second and 200 per minute per API key. See Rate Limits. |
| Money | Amounts are in USD. |
| Retries | The API has no idempotency keys. Check state before you repeat a request that buys something. |
{
"status": 200,
"message": "Domains fetched successfully",
"data": {}
}{
"status": 401,
"message": "Invalid API key",
"errorId": "6c0a0a4d-4a3e-4a9d-bf5d-0a2f7f5f4f31"
}status or data: wallet balance and top-up, Pre-Warmed purchase, quick setup, domain purchase and ZapShield purchase. The endpoint page for each one shows the exact shape.serviceProvider field with the value GOOGLE, MICROSOFT or null.null can appear on subscriptions and on domains that have no mailbox yet. Do not treat null as Microsoft.errorId from the response.