API Pricing and Credits
Some API endpoints consume Apollo credits. Credit consumption varies by Apollo plan. Check out the following sections to understand credits with Apollo API.
How API Credit Usage Works
Credit usage on API depends on the endpoint you call and whether Apollo finds credit-consuming data.
In general:
- Endpoints that create, update, list, or manage records don't consume credits.
- Enrichment, organization search, news search, and AI-insight endpoints may consume credits when qualifying data is returned.
- Credit usage is conditional; if Apollo doesn't find credit-consuming data, the request consumes 0 credits.
Page TurnerSome credit-consuming endpoints may use credits across multiple requests. If you paginate through results or run repeated searches, your total credit usage can increase. Before running a large workflow, test with a small request and verify credit usage in Apollo.
Endpoint Credit Usage
Check out the following table to understand whether an endpoint consumes credits and under what conditions. For your organization's exact credit consumption, review your Apollo plan and credit usage.
Estimate Credit Usage
Use the following approach before running a large API job:
- Identify whether the endpoint consumes credits with this table.
- Check the charging unit, such as per matched record or per page.
- Run a small test request of your workflow.
- Review your credit usage in Apollo.
- Scale the workflow after you understand the credit impact.
Track API Usage
You can review API usage and rate limits any time in Apollo.
Credit Usage
To view your credit usage, go to Settings > Billing and credits > Credit usage. You can check usage by team or individual.
Rate Limits
Apollo applies rate limits to API calls to protect platform performance and reliability. Rate limits vary by endpoint and your Apollo plan.
To view your rate limits, go to Settings > Integrations > API Usage. Alternatively, use the view usage endpoint to programmatically call usage data.
If you exceed a rate limit, Apollo returns a 429 Too Many Requests response. Reduce request volume, wait for the limit window to reset, or upgrade your plan if your workflow requires higher limits.