Limits are counted per API key. They are shared across all endpoints, all workspaces selected with x-workspace-key, and all API versions.
A request to a domain availability endpoint counts against all three limits.
Some keys have higher ceilings. Contact support@zapmail.ai with your use case if the defaults are not enough. The limiter runs before the key is validated, so requests that carry an invalid key also count against that key value. A request with no x-auth-zapmail header at all is rejected with 401 before the limiter runs.
Keep sustained traffic under 200 requests per minute, which is about 3 requests per second. The 5 per second ceiling only allows short bursts.
Poll at an interval of 15 to 30 seconds, not in a loop, and stop as soon as the resource reaches a final state. Better, subscribe to Webhooks and skip polling.
Cache data that rarely changes, such as the list of tags or workspaces.
Spread bulk jobs over time with a queue that caps the request rate for your key.