Rate Limits

Rate limits protect the API from abuse and ensure fair usage across all users. Each plan has different limits based on your subscription tier.

Rate Limits by Plan

How Rate Limiting Works

• Rate limits are calculated on a per-minute sliding window.
• Usage is also governed by your Credit System.
• When you exceed your RPM (Requests Per Minute) limit, requests return a 429 Too Many Requests error.

Rate Limit Response

When rate limited, you will receive:

{
    "statusCode": 429,
    "message": "Rate limit exceeded. Please wait before making more requests.",
    "data": null,
    "timestamp": "2026-01-10T03:42:00.000Z"
}

Rate Limit Monitoring

Track your rate limit usage through:

1. Dashboard Analytics

Monitor your API usage directly in the Fansly API Dashboard:

• Usage patterns – See how your API calls are distributed over time
• Peak usage times – Identify when you're making the most requests
• Rate limit warnings – Get alerts when approaching your limits

2. Response Headers

Response headers are included in every request to help you track your rate limit usage:

• X-RateLimit-Limit - The maximum number of requests you can make per minute.
• X-RateLimit-Remaining - The number of requests remaining in the current time window.
• X-RateLimit-Plan - The name of your current subscription plan.
• X-RateLimit-Retry-After - The number of seconds to wait before retrying (only present when rate limited).

Best Practices

• Implement exponential backoff – When you receive a 429 error, wait and retry with increasing delays.
• Cache responses – Avoid redundant API calls by caching data when possible.
• Monitor your usage – Check your remaining credits in the dashboard to avoid hitting limits.
• Batch operations – Where possible, combine multiple operations into fewer API calls.

Need Higher Limits?

If you need higher rate limits or custom quotas, contact our sales team to discuss Enterprise pricing.