Zapmail
Overview
API Reference
Overview
API Reference
  1. Capabilities
  • Introduction
  • Quickstart
  • Authentication
  • MCP
  • Versioning
  • Errors
  • Webhooks
  • Rate Limits
  • Pagination
  • Changelog
  • Capabilities
    • Mailboxes
    • Pre-Warmed
    • Deliverability
    • Domains
    • Export to Sequencer
    • Zapbox
    • Team Management
    • ZapShield
    • ZapCare
    • AI Insight
    • Deliverability Tests
    • ZapSites
    • Zapwarm
    • ZapPulse
  • Billing
    • Understanding Zapmail billing
    • Wallet
  1. Capabilities

ZapCare

Zap Care protects domains under a pay-as-you-go subscription billed per domain, monthly or annually. Domains covered by Zap Care are moved to Google Cloud DNS in the background, and zapCareEnabled turns on when the move is done. Lifetime Zap Care slots exist only for accounts migrated from the retired ZapShield lifetime plans and cannot be bought through the API.
Before you start: Zap Care subscriptions belong to the account, while allocations are listed per workspace. Fund your wallet first (see Wallet).

Protect domains#

1
Pick domains
GET /zap-care/eligible-domains lists ACTIVE domains that can be covered. A domain must have nameservers, must not be renewing, must have no Zap Care enabled or in progress and no ZapShield enabled, and must have been bought through Zapmail or connected with registrar credentials. The call always returns the first 100 domains, newest first, and has no filters or pagination.
2
Use existing capacity
GET /zap-care/available-slots returns free lifetime slots. POST /zap-care/allocate-domains turns on Zap Care using lifetime slots first. Remaining domains join your active pay-as-you-go subscription of the billingCycle you pass; without billingCycle they are left uncovered. It returns 400 when no domain could be covered, and 200 with uncovered greater than 0 when only some were. No invoice is created.
3
Or buy
POST /zap-care/purchase covers up to 100 domains in the workspace. Pass domainIds and a billingCycle of MONTHLY (default) or ANNUAL. Domains already covered by a lifetime slot are allocated at no cost and only the remainder is charged. Protected domains are skipped.
4
Confirm
Protection starts after the invoice is paid. Poll GET /zap-care/subscriptions and GET /zap-care/allocated-domains.
This charges your wallet. The key owner is charged. An invoice is created and settled from wallet credit, and any uncovered amount stays due on the hosted invoice at checkoutUrl.

Pricing in the endpoint specification#

USD 1.50 per domain per month or 9.00 per year, or 1.25 and 7.50 once the account already has 201 or more Zap Care domains. If an active subscription of the same cycle exists, the first charge is prorated to its remaining period, with a minimum of USD 0.50 per domain.

Read and cancel#

GET /zap-care/subscriptions returns one entry per domain allocation across all workspaces, not one per subscription, so a subscription with several domains appears several times. A subscription with no allocated domain is not listed. Take subscriptionId from it.
GET /zap-care/allocated-domains lists the domains under one subscriptionId in the current workspace. The default limit is 50 and the maximum is 100.
POST /zap-care/cancel-subscription cancels immediately and covers every domain on the subscription. Domains lose Zap Care, and their DNS is moved back by a background job unless ZapShield is still active. No refund is issued by this endpoint, and the cancellation cannot be reverted through the API.
Related: Deliverability, ZapShield, Domains.
Previous
ZapShield
Next
AI Insight
Built with