Developer API · updated 2026-10-13
Errors, rate limits and plan limits
The API uses a consistent error envelope, per-key rate limits, and a daily usage window on the free plan. This article documents every error code you can receive and exactly how the limits work, so your integration can handle each case gracefully.
- ## The error envelope
Every error is JSON with the same shape:
```
{ "error": { "code": "...", "message": "..." } }
```
Some errors add fields next to it (for example upgrade_url on plan-limit errors). Always branch on error.code, never on the human message, which can change. - ## HTTP status codes
200 success (and 200 with existing:true when a lead POST deduplicates), 201 lead created, 400 invalid_body or invalid_parameter, 401 unauthorized (missing, invalid or revoked key), 403 access_disabled (company gate turned off), 404 not_found, 405 method_not_allowed, 429 rate limit or daily volume reached, 500 internal (safe to retry with backoff). - ## Rate limit: 60 requests per minute per key
All plans. Exceeding it returns 429 with code rate_limited and a Retry-After header in seconds. Spread bursts or add a small queue; the counter resets each minute. - ## Free plan: the 10-minute daily window
On the free plan, your first API call of the day (company local time) opens a 10-minute window. Calls inside the window are served normally; after it closes, read calls return 429 with code daily_window_ended and an upgrade_url, until the next day. The X-DC-Window-Remaining response header tells you the seconds left. Design free-plan integrations as one scheduled sync burst per day. - ## Free plan: 200 leads per day
```
POST /v1/leads does NOT consume the 10-minute window (a lead can arrive at any hour). Instead the free plan includes 200 leads per day on their own count; beyond that you get 429 lead_quota_exceeded. The paid plan has no daily window and no daily lead count.
``` - ## Paid plan: higher volume
Companies on the optional paid plan have no daily window and no daily lead count. The technical 60 requests/minute per key limit still applies to protect the platform.
Troubleshooting
I got daily_window_ended but I barely made any calls.
The window is time-based, not call-based: it runs for 10 continuous minutes from your FIRST call of the day, whether you call once or a hundred times. Batch your work into that window.
Do webhooks count against my window?
No. Webhooks are pushed by us and never consume your window or rate limit.
Related guides
© 2026 Dumpster Controls. All rights reserved. Made in the USA.