Skip to main content
Truthlocks enforces rate limits to ensure fair usage and platform stability. This guide explains limits by tier and how to handle rate limiting gracefully.

Limits by Tier

Burst Capacity: All tiers include 2x burst capacity for up to 10 seconds. This allows handling traffic spikes without immediate rate limiting.

Per-Endpoint Limits

Some endpoints have additional specific limits:

Rate Limit Headers

Every API response includes headers to help you track your usage:

Handling 429 Responses

When you exceed the rate limit, you’ll receive a 429 status code:
Important: Always respect the Retry-After header. Repeatedly hitting rate limits may result in temporary IP blocks.

Best Practices

Exponential Backoff

Request Batching

Monitor Usage

Requesting Quota Increases

If your usage requires higher limits:
  1. Starter/Professional: Contact support with your use case and expected volume
  2. Enterprise: Custom limits are negotiated during contract discussions
  3. Temporary Increase: For events or migrations, request a temporary burst increase 48 hours in advance
Tip: Include metrics showing your current usage patterns and growth projections when requesting increases.

Next Steps

Health & Readiness

Monitor API health and your integration status.

SDK Examples

See rate limit handling in real code.