Rate limits - The Data City

The Data City API throttles per-minute request volume to protect the service for every customer.

Limits

Endpoint group	Limit
Customer v2 API (`/v2/...`)	200 requests per minute
Internal admin (`/admin/...`)	60 requests per minute

The limit is applied per authenticated token. Each request counts as one, regardless of the response status or payload size.

When you exceed the per-minute quota, the API responds with:

HTTP/1.1 429 Too Many Requests
Content-Type: application/json

{"message":"Too Many Attempts."}

See Errors for the full envelope and other status codes.

Retry 429 responses with exponential backoff. A pragmatic starting point:

attempt 1 → wait 2 s
attempt 2 → wait 4 s
attempt 3 → wait 8 s
attempt 4 → give up, surface the error

Add a small random jitter (0–500 ms) so concurrent clients don’t synchronise their retries.

If you have a workload that comes near 200/min:

Batch where the API supports it. Endpoints like /v2/companies/batch, /v2/companies/by-website/batch, and /v2/companies/check take many inputs in a single request — one HTTP call instead of many.
Use company-number sets for large portfolios. Filtering against a 200k-company set is one request, not 200,000.
Cache stable data. Company details don’t change second-to-second; cache results for as long as your domain tolerates staleness.

If your use case genuinely needs a higher steady-state rate, email support@thedatacity.com.