Surfer API Rate Limits & Quotas

⏱ Rate limits

All endpoints enforce a per-second or per-minute rate limit. Exceeding it returns 429 Too Many Requests.

When you hit a 429, wait before retrying. Check the x-ratelimit-reset header (a Unix timestamp) to see when the rate-limit window resets, then retry. Use exponential backoff for automated workflows.

Monitoring rate limits via response headers

Every V2 API response includes these headers so you can track limits before hitting them:

Reading x-ratelimit-remaining in your integration lets you slow down proactively instead of waiting for a 429.

📊 Usage quotas

Quotas are separate from rate limits, they track how many queries you've consumed in a billing period. Limits below are per our Fair Usage Policy for Peace of Mind. While Enterprise limits are custom, contact your Customer Success Manager to verify your quota or check your Usage dashboard under Settings.

Note: There is currently no API endpoint to check remaining credits or quota usage programmatically. To avoid hitting limits mid-run, track your own usage or check your dashboard before large batch jobs.

Additional resources:

Surfer API Introduction

Surfer API Documentation (v1)

Surfer API Documentation (v2)

Surfer API Examples of Use