Apollo Credits Explained in

• In the app, Apollo says accessing a verified email or any phone number for a net-new contact can consume credits✓. 2
• In the API, some record-management endpoints use zero credits, while people enrichment and organization search have documented charging units✓. 1
• Apollo's usage view can separate API from web-app activity and show refunds✓. 3

1. Begin with the event, not the headline credit balance

A balance tells you how much capacity remains; it does not tell you which action will use it. Apollo's API documentation says credit use depends on the endpoint called and the data returned✓. Its usage guide says features and actions visible in history depend on the workspace's plan, configuration and prior activity✓. Before estimating a campaign or enrichment job, write an inventory of the exact actions the team will perform. Separate email access, phone access, organization search, people enrichment, exports and any automation. 13

Treat plan entitlements as a different question. The public pricing page could not be reliably rendered in this research session, so this article does not claim a current plan's included number of credits, subscription price or feature entitlement. Apollo also warns that API credit behavior may differ on legacy plans✓. The only reliable account-specific answer is the entitlement and usage view in your own workspace or a current written quote. 1

2. In-app data requests: what Apollo says is charged

Apollo defines a data request as contact information purchased with credits. Its help article says that when a user clicks Access email or Access mobile for a net-new prospect, Apollo searches for verified information and charges when a verified email or any phone number is accessed✓. That is a data-access event. It should not be conflated with every later action involving the saved contact. 2

A useful exception appears in the same help article: when an email is requested, Apollo automatically looks for a verified office phone number and says it does not charge additional credits for accessing that office number✓. This does not establish that every type of phone access is free. It is a narrow rule tied to the automatic office-phone lookup during an email request. If a team requires mobiles, confirm the exact action and resulting charge in the account. 2

Apollo also describes a specific refund condition: an Apollo-verified email requested, messaged from Apollo within 30 days, and subsequently bounced can lead to a next-cycle credit refund. The same article says this does not apply to mobile numbers✓. Do not subtract hypothetical refunds from a procurement estimate as though they are guaranteed. They depend on the described workflow and timing, and the credit usage view should be checked to see the actual refund event. 23

3. API credits: endpoint and returned data determine the bill

Apollo's developer page makes a broad distinction: API endpoints for creating, updating, listing or managing records consume zero credits, while enrichment, organization search, news search and AI insight endpoints may consume credits when qualifying data returns✓. That is not a promise that an entire integration will be free. An application may call several endpoints in one workflow, and Apollo warns repeated searches or paginated results can raise total usage✓. 1

For people enrichment, the current developer table lists 1 to 9 credits per person when credit-consuming data is found: one credit for demographics or email and eight more when a mobile phone is returned✓. Bulk people enrichment uses the same per-person logic for up to ten people in a request✓. The request size is therefore not the charge unit. Ten matched people in one bulk request are not automatically one credit. 1

For organization data, the table lists one credit per organization for organization enrichment and one credit per page for organization search, with up to 100 results per page✓. This is why an estimate must distinguish records from result pages. If a job searches many pages and then enriches selected organizations, count both documented charging events rather than multiplying every account by one assumed flat rate. 1

Waterfall enrichment introduces another exception. Apollo says charging depends on returned data and the configured vendors, and some vendors charge per lookup even if no data is found✓. Therefore, the ordinary people-enrichment range is not a universal ceiling for every waterfall workflow. Run a small representative batch with the intended configuration before projecting the cost of thousands of records. 1

4. Credits renew, and unused capacity has a real cost

Apollo's credits overview says credits expire at the end of each billing cycle and do not roll over✓. It says renewal occurs on the first day of the cycle, with annual-billing release timing that can depend on billing arrangement✓. These statements matter because an oversized allocation can expire while a seasonal team uses less than expected. The practical forecast should use the team's likely activity by cycle, not only an annual total. 4

For a pilot, estimate how many net-new contacts need email, how many need mobile, how many organizations must be searched or enriched, and how many API pages the job will traverse. Then compare that modeled demand with the actual usage history after a week. If the gap is large, diagnose whether the model missed a second endpoint, waterfall lookup, export or automation. Do not infer consumption from the headline plan name.

5. Audit usage by feature, surface and refund

Apollo's usage page documents filtering by surface, including API and Web App, and an option to show refunded credits✓. That lets a team distinguish a rep's in-app data requests from an automated API job. The same page warns that the visible feature and action history depends on configuration, plan and historical usage✓. A missing line item is not proof that an action always costs zero credits; inspect the relevant account context. 3

Create a weekly review with opening balance, new allocation, usage by feature, usage by surface, refunds and closing balance. Tag the business workflow that created the demand. A raw credit total is not enough to determine whether the spend produced useful contacts or pipeline. Connect the audited usage to accepted records, contacts worked and qualified conversations, while preserving the distinction between data access and a business outcome.

6. A worked estimate, not a quoted plan price

Suppose a test calls people enrichment for 100 records, each returning only the credit-consuming demographics or email described by Apollo's API table. The table's unit would imply 100 credits in that simplified scenario✓. If all 100 also returned a mobile under that same endpoint, the documented one-plus-eight logic would imply up to 900 credits for those matched records✓. This arithmetic is a hypothetical model, not a promise of actual billing. Waterfall configuration, returned data and legacy-plan rules can change the result✓. 1

Run the actual request in a small batch, inspect the credit ledger, and revise the estimate before increasing volume. For search-driven workflows, remember Apollo's organization search is per result page rather than per organization✓. Do not mix it into the people-enrichment line. 1

FAQ

How we researched this

We captured Apollo's current developer API credit page, data-request help article, credit-usage guide and credits overview on October 1, 2026. Each product statement maps to an exact dated excerpt. We attempted to render Apollo's current pricing page in headless Chrome; it crashed, so we omitted current plan entitlements and dollar prices. We did not use older plan tables as a substitute for a live plan check.

Make credits serve the workflow

Modern Inbound can help define the research, list-building and outbound workflow before credits are spent at scale. Discuss a measured outbound system, or email [rish@moderninbound.com](mailto:rish@moderninbound.com).