Apollo.io Credits and Exports: What Uses Them and Why

Credits are the part of Apollo people understand last and worry about first. The confusion is reasonable, because there is more than one kind, they are spent by actions that do not feel like purchases, and the balance can look fine right up until an enrolment refuses to run.

This guide covers what actually consumes them, according to Apollo's own documentation, where to read your history, how export credits differ from the rest, and the habits that stop you burning through a month's allowance in an afternoon.

The mental model that helps: you are not paying for clicks, you are paying for facts Apollo has not given you before. Once you hold that idea, most of the surprises stop being surprising.

What are credits in Apollo?

Apollo defines them as the thing that lets you access data and use certain features. Its documentation says that depending on your plan, your team may use credits to reveal emails and phone numbers, enrich records, run AI-powered research, use email warmup and complete other credit-consuming actions.

There is one detail in there that catches people out repeatedly. Apollo states that email and mobile data use separate credit balances. Having plenty of one does not mean you have any of the other.

Which features actually consume credits?

Apollo publishes the full list on its credit usage page. Not every row applies to every account, and their documentation notes that the features and actions you see depend on your plan, workspace configuration and usage history.

Two of those rows are worth a second look because they surprise people. Email warmup shows up under email infrastructure, so the deliverability work you set up and forget about is quietly drawing on the same budget. And AI research covers the AI assistant, so asking Apollo's assistant to do your prospecting for you is not free.

How do you see where your credits went?

Apollo's credit usage history is the honest answer to any argument about who spent what. It is more detailed than most people expect.

Reading your credit usage history

1. Open billing — Launch Apollo and click Settings, then Billing.
2. Open the history — Click Credit usage and AI, then History.
3. Filter it — Narrow by Date for a time period, by Team member for a specific user, or by Feature for a specific feature or feature group.
4. Read the graph, then the table — The graph shows the trend. The table shows individual events, with columns for Date, Feature, Action, Description, Credits, Data requested and User.
5. Include refunds — Enable Show refunds to see refunded credits in the table alongside the spend.

Apollo's other documentation pages point at slightly different paths, including Settings then Manage Plan, and Settings then Credits. Those pages have been moving, so if one route is missing on your account, try another rather than assuming the feature is gone.

What does building a list or a sequence cost?

These are the two numbers most people want, and Apollo states both plainly in its own documentation.

• Adding to a list: Apollo states it costs one email credit per verified email to add net new contacts to a list, and that adding previously saved contacts costs nothing.
• Adding to a sequence: Apollo states it charges one credit per net-new verified contact you add to a sequence, and that there is no charge for adding a saved contact who already has a verified email.
• Saving from LinkedIn: Apollo's Chrome extension documentation states that saving contacts costs credits, and revealing a phone number is a separate request from revealing an email.
• Exporting: Apollo states that exporting prospects also saves them as contacts in your account, so an export is never a neutral read.

The pattern across all four is the same. Net new costs you, already saved does not. That single rule explains more of your bill than any pricing table.

It also explains the most common piece of waste. Building a large list, glancing at it, discarding it and building it again spends credits every single time, because each rebuild pulls fresh records you have never held.

Why do I get a credit warning when my balance is fine?

Apollo answers this directly on its sequence documentation, and the answer is reassuring. A credit warning can appear even when your balance looks healthy, usually because waterfall enrichment is pulling from paid providers, because validation is switched on, or because the preview is showing the maximum possible spend rather than the likely one.

Their guidance is to check your credit settings or your waterfall enrichment report for the actual usage rather than trusting the warning's estimate. Apollo also notes that it may check credits for a full batch before enrolment begins, which is why a warning can fire before anything has been spent at all.

How are export credits different?

Export credits govern data leaving Apollo, not data entering your workspace. Apollo's pricing page states that you consume export credits whenever you export a contact outside of Apollo, giving CSV, CRM or Person API enrichment synced to an outside system as its examples.

The exemptions matter more than the rule. Apollo's export documentation states that contacts already exported, contacts imported from CRM, CSV, manual or API sources, and contacts without verified emails do not consume export credits.

Their credit usage page adds a caveat worth reading carefully: export credits may only apply to certain plans or legacy configurations. So if you cannot find an export credit balance on your account, that may be correct rather than a bug.

How do you export contacts to a CSV?

Exporting contacts to a CSV

1. Enrich first — Apollo notes that exporting existing records does not automatically enrich emails and mobile numbers. Enrich the contacts before you export, or the columns arrive empty.
2. Open the search — Launch Apollo and click Search, then People. Apply filters, or use a saved search or a list.
3. Select and export — Check the contacts you want, or use bulk selection along the top, then click Export.
4. Choose which emails — Decide whether to export emails for every contact you selected, or only for those with verified emails.
5. Set the columns — Click Edit export CSV settings to adjust the fields included. Apollo warns that emails and phone numbers are not always included by default, and that unselected fields arrive as blank columns even when the data exists.
6. Run it and collect it — Click Export records. Exports over about 1,000 contacts may take several minutes. Check progress under Settings, then Import and Exports, then CSV Exports, and click Download when it finishes.

Two small gotchas Apollo documents. CSV exports may not keep the sort order you saw on screen, so sort in your spreadsheet afterwards. And spreadsheet apps reformat postcodes, phone numbers and long IDs, so import those columns as text if the exact characters matter.

Does pushing to a CRM count as an export?

Apollo's pricing page treats syncing data to a system outside Apollo as export credit usage, and names Outreach and Salesloft as examples. A connected CRM integration is a slightly different case, because it is a managed sync rather than a one-off push.

For HubSpot, Apollo documents two versions of the integration. HubSpot CRM is a bi-directional sync that pushes and pulls contacts, accounts and deals and pushes activities such as calls, emails, meetings, tasks and notes. HubSpot Data Enrichment is enrichment only and does not sync or push records.

Apollo also warns that it mirrors what is in HubSpot, duplicates included, and recommends deduplicating your CRM before connecting. That is good advice and it is easy to skip, because the mess is invisible until it is in two systems instead of one.

What do the plans include?

Reading Apollo's own pricing page on 17 August 2026, the compare-plans row listed a Free plan at zero dollars with 900 credits, Basic at 49 dollars per seat per month billed annually with 30,000 credits, Professional at 79 dollars per seat per month billed annually with 48,000 credits, and Organization at 119 dollars per seat per month with a three seat minimum, billed annually, with 72,000 credits.

The Organization plan card described its allowance as credits per seat per year, granted upfront, which suggests the other figures are annual per-seat allowances too. Pricing and packaging change often, so treat these as what was on the page that day and confirm the current numbers yourself before you budget.

Their pricing FAQ adds several details worth knowing. Trial plans include 50 credits and 5 mobile credits along with almost all features of the plan you picked, but not the ability to link a non-Gmail or non-Microsoft account. After a trial you can convert to a paid plan or drop to the free Starter plan. You can buy additional credits at any time once logged in.

The same FAQ describes a record selection limit, which caps how many new records you can select from the database at once, and a fair use policy that governs unlimited plans with a stated ceiling on credits per account. It also notes that some features are only available on Apollo's newer credit system, with existing customers being moved across gradually. If a feature described here is missing from your account, that is a likely reason.

How to stop wasting credits

• Filter before you reveal. Narrow the search until the count is realistic, then commit. Every speculative bulk save is a purchase.
• Cap people per company. Apollo's bulk selection offers a max people per company setting. Forty contacts at one employer is forty credits for one conversation.
• Use saved searches instead of rebuilding. A saved search returns to the same criteria without repurchasing the same records.
• Check the history before you argue. The usage table names the user and the feature for every event, so the answer to where did the credits go is always available.
• Remember warmup and AI draw from the pot. Email infrastructure and AI research both appear on Apollo's credit-consuming list, and neither feels like a data purchase while you use it.
• Watch the second balance. Email and mobile credits are separate. Running out of one while the other looks healthy is normal, not a glitch.

A different way to think about the meter

Step back and look at what this article has been about. Not how to sell to anyone, but how to manage a metered data budget across several separate balances while avoiding the actions that quietly spend it.

Overhead like this is exactly what we removed at Sistava. Rather than budgeting record lookups, you hire an AI Employee and tell it in plain English what outcome you want. It has its tools connected already, it asks you when it is unsure, and it sets itself up, so the thing you are paying for is work done rather than rows retrieved.

To be fair to Apollo, a credit model is an honest way to price a database. It means light users are not funding heavy ones, and the usage history it exposes is genuinely detailed compared with most vendors. If your business runs on volume prospecting, that transparency is worth having. If it does not, the meter is a thing you now have to think about every week.

Sources

• Apollo Knowledge Base, Review Credit Usage in Apollo
• Apollo Knowledge Base, Export Contacts to a CSV
• Apollo Knowledge Base, Add Contacts to a Sequence
• Apollo Knowledge Base, Create and Use a List
• Apollo Knowledge Base, Integrate HubSpot with Apollo
• Apollo.io, Pricing plans and FAQ