Rate Limits & Credits
This page explains how credits and rate limits work across all TopYappers APIs.Credits Pricing
Each API call consumes credits based on the data returned:| API | Endpoint | Cost |
|---|---|---|
| Creators API v1 | GET /api/v1/creators | 1 credit per creator |
| Creators API v2 | GET /api/v2/creators/search | Free |
| Creators API v2 | POST /api/v2/creators/get | 1 credit per creator |
| Videos API | GET /api/v1/videos | 1 credit per video |
| Viral Content API | POST /api/v1/viral-content | 1 credit per content |
Rate Limits
All API endpoints are rate limited to 60 requests per minute per API key. When you exceed the rate limit, you’ll receive a429 Too Many Requests response with a Retry-After header indicating how many seconds to wait.
Response Headers
Every API response includes headers to help you track your usage:x-ty-credits
Your remaining credit balance after the request.
x-ty-rate-limit-remaining
Number of requests remaining in the current rate limit window (resets every minute).
x-ty-rate-limit-total
Your total rate limit allocation per minute. Default is 60 requests/minute.
Need higher rate limits? If you require increased rate limits for your use case, please contact support to discuss enterprise options.
Example Response Headers
Handling Rate Limits
Here’s how to properly handle rate limits in your code:Best Practices
Monitor Your Usage
Check the
x-ty-credits header regularly to avoid running out of credits mid-operation.Use v2 Search
The v2 search endpoint is free - use it to find exactly the creators you need before fetching full profiles.
Implement Backoff
When you hit rate limits, respect the
retryAfter value and implement exponential backoff.Batch Requests
Use pagination efficiently and batch your requests to stay within rate limits.
