Skip to main content

Rate Limits

All API requests are rate limited per organization to ensure fair usage and platform stability.

Default Limits

Per-organization overrides are available on enterprise plans. Contact support@dealmachine.com to discuss higher limits.

Response Headers

Every API response includes rate limit headers so you can track your usage in real time:

429 Response

When you exceed the rate limit, the API returns a 429 Too Many Requests response:
The response also includes a Retry-After header with the number of seconds to wait before retrying.

Exponential Backoff

When you receive a 429 or 5xx response, use exponential backoff to retry. This means waiting progressively longer between retries:
  1. Wait 1 second, then retry
  2. If still failing, wait 2 seconds, then retry
  3. Then 4 seconds, 8 seconds, 16 seconds
  4. Cap the maximum wait at 30 seconds
Add a small random jitter (0-500ms) to each wait to prevent thundering herd problems when multiple clients retry simultaneously.

JavaScript / TypeScript

Python

Best Practices

All enrichment and batch endpoints accept up to 250 items per request. Batching reduces your request count significantly — 250 addresses in a single request counts as 1 request toward your rate limit.