LeadTale API Docs

Rate Limits

Request budgets for the LeadTale API.

The LeadTale API enforces rate limits to protect against abuse and ensure fair usage.

Per-IP global limit

1000 requests per 15-minute window per source IP, across all /api/v1/* routes. Enforced at the edge before any API-key validation.

Exceed the limit → HTTP 429 Too Many Requests:

{
  "statusCode": 429,
  "message": "Too many requests, please try again later."
}

Plan-based daily limits

Your account also has plan-based limits:

  • Requests per day — total request volume
  • Unique contacts per month — distinct contact records returned

Exact numbers depend on your tier. Check usage at Account → Billing & Usage.

When a plan limit is exceeded, requests return HTTP 429 with a body indicating the specific limit:

{
  "statusCode": 429,
  "message": "Daily request limit exceeded for your plan. Upgrade at https://app.leadtale.com/billing."
}

Response headers

Every response includes:

  • X-RateLimit-Limit
  • X-RateLimit-Remaining
  • X-RateLimit-Reset (Unix epoch seconds)

Use these to back off proactively.

Retry guidance

On 429, wait until X-RateLimit-Reset (or exponential backoff if absent). Don't tight-loop retry — repeated 429s extend the cooldown.

On this page