Understanding credit allocation and subscription plans
Please refer to the table below to get a general overview of the credit cost for our endpoints.
For detailed information about where to find credit information in API responses, see our Response Structure documentation.
Endpoint(s) | Cost | Notes |
---|---|---|
Search Profiles | 1 credit per result | E.g. if your search query has 10 results, you will be debited 10 credits. |
Media Uploading | 6 credits per MB | For easy calculation, we use decimal measurements. This means that 1MB is 1,000 KB. |
Media Scraping | 6 credits per MB | For easy calculation, we use decimal measurements. This means that 1MB is 1,000 KB. |
Webhooks | 1 credit per sent webhook event | E.g. if you have one webhook configured for both messages.received and messages.sent , you will be charged 1 credit every time one of those events is triggered. Webhooks are not sent as a bundle, so every event is 1 credit. |
All other uncached responses | 1 credit per request | - |
All other cached responses | 0 credits | - |
Public endpoints make use of automatic caching by default, and thus won’t cost you any credits if a cached response already exists.
Account-specific endpoints will never be cached, and will always give you a fresh response from OnlyFans.
You can force a fresh response by appending the endpoint URL with ?fresh=true
All account-specific endpoints, and endpoints that reply on real-time data, will always return a fresh response from OnlyFans and thus will consume credits.
Our subscription tiers provide different credit allocations:
• Perfect for small to medium projects
• Includes all basic features
• Automatic credit tracking
• Ideal for larger applications
• Priority support
• Advanced features included
• Tailored to your needs
• Contact us to discuss requirements
• Custom features and support
All subscription tiers include:
• Up to 200% of monthly allocation
• Automatic rollover management
• No manual activation required
• Real-time balance tracking
• Detailed usage analytics
• Automated notifications
• Automatic response caching
• Zero-credit cached responses
• Cache control with ?fresh=true
You can easily track your credit usage through all of our API responses, and via our Console
Best practices for optimizing credit usage:
Leverage cached responses when possible.
Monitor your credit balance regularly.
Review usage patterns regularly. Consider optimizing your requests.
Cached responses are free and don’t consume any credits from your balance. This applies to public endpoints like profile information.
For high-volume requirements, we offer:
Please contact our team to discuss your specific needs and get a tailored solution.