--- title: "Findymail API review: credits back above 5% bounce" description: "What the Findymail API costs per email and phone, the bounce guarantee, the concurrency limits in place of a rate limit, and which calls charge on a miss." url: https://frontal.so/gtm-apis/enrichment-apis/findymail-api-review updated: 2026-11-12 --- # Findymail API review A refund if your bounce rate passes 5% Reviewed by **Frontal** *·*Updated October 2026 ## On this page 1. What a call costs 2. Pricing and plans 3. Rate limits 4. API key and access 5. Request example 6. Docs and reference 7. Video walkthrough 8. Strengths and limits 9. Verdict 10. Before you build 11. Top alternatives 12. Head to head [Visit Findymail](https://www.findymail.com/) **From** $99/mo **Unit cost** $0.0198 per credit **Billing** Subscription Credit packs **Best for** A refund if your bounce rate passes 5% find-email.sh 1 finder credit ``` POST https://app.findymail.com/api/search/name Authorization: Bearer $FINDYMAIL_KEY { "name": "Jane Doe", "domain": "acme.com" } # 1 credit only if a verified email is found # limited by simultaneous requests, not per second ``` 200 OK Per credit, Starter plan $0.0198 The Findymail API finds a work email from a name and a company, and verifies it in the same step, so you are not paying a second provider to check what the first one found. It is the only provider in this directory that puts a number on deliverability and refunds against it: if your bounce rate on Findymail emails goes above 5%, the credits come back. Findymail now sells two ways. Prospecting for your own team is a usage-based plan with seats, from $99 a month for one seat. Reselling the data or embedding it in your own product is a credit plan, from $99 a month for 5,000 finder credits, which is $0.0198 an email, plus 5,000 verifier credits for addresses you got somewhere else. On credits, one is spent only when a verified email is found, a mobile costs 10, and an email found again within 30 days costs nothing. The API has grown well past the finder. The current docs cover phone lookups, reverse email, company and employee search, lookalike companies, technologies by domain and hiring signals, each with its own credit rule. The rule worth reading first is that the finder charges on success while the verifier charges on every attempt. The rest of the category is in the [Enrichment APIs](https://frontal.so/gtm-apis/enrichment-apis) listing. ## Which calls charge, and when Findymail meters two balances, finder credits and verifier credits, and most endpoints draw on the finder balance only when they return something. The exceptions are the ones to design around. | Endpoint | What it does | Credits | | --- | --- | --- | | /api/search/name | A verified email from a name and a domain or company name. | 1 finder, only if found | | /api/search/business-profile | A verified email from a professional profile URL. | 1 finder, only if found | | /api/search/phone | A mobile number from a profile URL. Non-EU only. | 10 finder, only if found | | /api/verify | Checks an address you already have. | 1 verifier, on every attempt | | /api/search/reverse-email | The profile behind an email address. | 1 finder if found, 2 with full profile data | | /api/search/company | Company information. | 1 finder, only if found | | /api/search/employees | Contacts at a company. | 1 per contact found | | /api/lookalike/search | Companies similar to one you give it. | 1 finder per 10 results | | /api/technologies | Technologies a domain uses. | 1 finder if found, free if not | | /api/credits | Both remaining balances. | Free | Intellimatch, the plain-language list builder, runs as a job: you submit a query, poll its status and collect the results, and it charges 1 credit per email and 10 per phone it finds if you ask it to enrich. Signals lets you create monitors that post matches to a webhook. Find from domain is deprecated The endpoint that finds a contact by domain and role is limited to 5 concurrent requests, can take up to 24 hours when run asynchronously, and is marked deprecated in the docs. Findymail points to the employees endpoint instead. Older tutorials still use the domain one. ## Findymail API pricing, plan by plan Findymail API pricing comes in two kinds, and API and MCP access are included on every plan. Usage-based plans are for your own team: Individual at $99 a month with 1 seat, Team at $399 with 5 and Scale at $999 with 20. Credit-based plans are for anyone reselling or embedding the data, from $99 a month for 5,000 finder credits. ### Free $0 10 credits, once - No card required - Enough to see the shape of a response - Not a monthly allowance ### Starter $99 /mo, 5,000 finder credits - Plus 5,000 verifier credits a month - $0.0198 per email found - Unused credits roll over, up to twice the monthly allowance ### Individual $99 /mo, 1 seat, usage-based - For your own team only, not for reselling - Usage is not counted in credits - 25 simultaneous API requests ### Team $399 /mo, 5 seats, usage-based - Five times the usage of Individual - 25 active signals - 50 simultaneous API requests ### Scale $999 /mo, 20 seats, usage-based - Twenty times the usage of Individual - 100 active signals - 150 simultaneous API requests ### Enterprise Custom volume pricing - Custom usage, seats and signals - Priority support and a dedicated account manager Starter is the credit plan, and it is the only credit tier Findymail publishes; larger volumes are custom. The usage-based plans do not count credits at all: when a plan reaches its limit nothing is charged, and you wait or move up. Paying yearly is advertised as two months free. Datacare, the CRM hygiene product, is priced separately from $500 a month billed annually. The guarantee is in credits, not cash Findymail says that if your bounce rate on its emails goes above 5%, it refunds your credits, and that most customers see 0 to 2% when sending without re-verifying. The refund is credits back on the account. Keep your own bounce data by source, because that is the evidence a claim rests on. Built in Clay ### Building this yourself? *Start in Clay.* Clay runs a waterfall across 150+ data providers from one table, without a separate contract with each. A lookup that finds nothing costs no data credit. **150+** data providers **500** free actions a month **$0** for a miss [Try Clay](https://go.frontal.so/clay) Frontal is a Clay Elite Studio Partner. A Clay waterfall **Clay** ## Concurrency, not requests a second Findymail API rate limits are expressed as simultaneous requests rather than as a rate. Concurrency-limited endpoints allow 300 requests in flight by default, and on the Individual, Team and Scale plans that drops to 25, 50 or 150, shared by the whole team. Some endpoints carry a lower ceiling of their own. | Endpoint or plan | Limit | Note | | --- | --- | --- | | Default | 300 simultaneous | Unless an endpoint or plan states otherwise | | Individual plan | 25 simultaneous | Shared by the whole team | | Team plan | 50 simultaneous | Shared by the whole team | | Scale plan | 150 simultaneous | Shared by the whole team | | Find from business profile | 30 simultaneous | When called synchronously | | Find from domain | 5 simultaneous | Deprecated; async can take 24 hours | | Search technologies | 10 a minute | Free endpoint | ### What concurrency means for a pipeline The ceiling is how many calls are open, not how fast you send them. - A find that takes a few seconds holds a slot for a few seconds. - Size your worker pool to the plan's number, not to a per-second rate. - The cap is shared, so a teammate's bulk job takes slots from yours. - Pass a webhook\_url and the finder runs in the background and posts the result. ### Which figure is yours The docs and the pricing page now use the same names. - Individual, Team and Scale are the plan names on the pricing page. - So the figure for a usage-based plan is 25, 50 or 150. - The credit-based Starter plan is not named in the concurrency docs. - On credits, ask Findymail whether the 300 default applies before you size a pool. A 402 means you are out of credits When the balance runs out, the API answers 402 with "Not enough credits". It is not a rate limit and retrying will not help. Read the balance from the credits endpoint, which is free, and stop the job rather than backing off. Concurrency limits are friendlier than per-second limits for slow, real-time lookups, because a waiting call costs you a slot rather than a rejection. The catch is the credit plan, whose figure the docs do not state; get it in writing before you build a worker pool around it. ## How to create a Findymail API key A Findymail API key is created on the API tokens page of the app, and Findymail lists API access as free on all plans. Every request sends it as a Bearer token in the Authorization header, and the base URL for every endpoint is app.findymail.com. ### Getting a key Free account first, then the token. - Sign up for a free account, no card, with 10 credits. - Open the API tokens page and create a token. - Send it as Authorization: Bearer YOUR\_KEY. - Credits are shared across the team, so one key can serve one pipeline. ### Spending the 10 free credits well Ten is enough to test the integration, not the data. - Use them on rows where you already know the right answer. - A miss costs nothing on the finder, so test on hard rows too. - Do not spend them on the verifier, which charges every attempt. - Judge match rate on a paid month, against your own list. There is not much to the credential itself; the decision that matters is which balance a call draws on. Keep finding and verifying in separate code paths, so the verifier's charge-on-every-attempt rule never runs on addresses Findymail already verified when it found them. ## What a Findymail API call looks like The finder is a POST with a JSON body: a name, and either a domain or a company name. Add a webhook\_url and the search happens in the background, with the result posted to your URL when it finishes. findymail.sh concurrency-limited ``` # 1. find and verify in one step POST https://app.findymail.com/api/search/name Authorization: Bearer $FINDYMAIL_KEY { "name": "Jane Doe", "domain": "acme.com" } # 2. both balances, free GET https://app.findymail.com/api/credits # { "credits": 150, "verifier_credits": 100 } ``` 402 Out of credits Stop, do not retry ## Where the Findymail API documentation lives The Findymail API docs are a single reference page at app.findymail.com/docs, with an example request in several languages for every endpoint. Findymail also publishes a Postman collection and an OpenAPI spec there. The developer documentation used to live on a separate host that no longer answers, so older links in tutorials are dead. | Surface | Where | What it answers | | --- | --- | --- | | API documentation | app.findymail.com/docs | Every endpoint, its credit rule and its concurrency limit. | | OpenAPI spec | app.findymail.com/docs/openapi.yaml | The whole API, to generate a client from. | | Postman collection | app.findymail.com/docs/collection.json | Every request, ready to run. | | API tokens | app.findymail.com/user/api-tokens | Create and manage keys. | | Pricing | findymail.com/pricing | Credits, the guarantee and the rollover rule. | The reference was last updated on July 31, 2026, according to the page itself, and it is the only source that states the concurrency figures. The pricing page states the guarantee and the rollover rule, and neither page states both, so read the two together. The [MCP page](https://frontal.so/gtm-apis/mcp-servers) lists Findymail's MCP access alongside the others in this directory. ## Findymail's own product walkthrough Findymail publishes this on its own channel, so it is Findymail's account of Findymail, not ours. It is here because a rate card cannot show you the thing moving, and a few minutes of the product is faster than any paragraph on this page at telling you whether the shape of it fits yours. [YouTube · Findymail Full Findymail.com Tutorial 2025 (Best B2B Data) 12:15 · Published October 2025](https://www.youtube.com/watch?v=kKttYPk9lVQ) Twelve minutes from October 2025, chaptered by product: Intellimatch list building, Datacare, the email finder, the mobile finder, email validation, and API integrations at 11:14. It is a product tour, and the accuracy claims in it are Findymail's own. The guarantee this page leans on is the one written on the pricing page, not the one in the video. Published 24 October 2025 on [Findymail](https://www.youtube.com/channel/UCEje7qcMmW7Ya4m8KWsfosQ), the channel Findymail's own pages link to, and read on 23 October 2026. Nothing in it is a source for a price or a limit on this page: every figure in the tables above comes from a Findymail page. ## Strengths and limits Findymail is priced like a commodity finder and sold on the one thing commodity finders will not promise. ### What it does well - Verifies at the moment it finds, so there is no second verification bill. - Credits refunded if your bounce rate on its emails goes above 5%. - A finder credit is spent only when a verified email is found. - An email found again within 30 days costs nothing. - Unused credits roll over, up to twice the monthly allowance. - Credit plans are shared across a team, with no per-seat charge. - API and MCP access on every plan. ### Where it falls short - Only one credit-based tier is published; larger credit volumes are a call. - The verifier charges on every attempt, unlike the finder. - Mobile numbers are non-EU only, at 10 credits each. - Usage-based plans state their usage as multiples, not as a number of emails. - Usage-based plans are for your own team only, so an embed needs the credit plan. The two columns say the same thing from both sides: Findymail is a finder with an honest promise attached and a pricing page that states usage as multiples rather than numbers. The guarantee and the charge-on-success rule make it cheap to test seriously; the unstated volumes mean you will be on a call before you scale. ## Who should actually buy this Buy Findymail when bounces are the cost you are trying to remove, because it is the only provider here that refunds against a bounce rate. It suits a cold email team that sends straight from what it finds and wants the finder to carry the deliverability risk. Do not run its results through a separate verifier. Findymail verifies when it finds, and the practitioners quoted on this site are blunt about paying twice for one answer. The verifier credits in the plan are for addresses that came from somewhere else. Pick the plan by what you do with the data. Prospecting for your own team belongs on a usage-based plan. Reselling or embedding needs the credit plan, where the price above 5,000 emails a month is not published, so treat Starter as a test of match rate on your own list and negotiate the volume with that number in hand. Findymail is the first pick on the [Dropcontact alternatives](https://frontal.so/gtm-apis/alternatives/dropcontact-alternatives) page: like Dropcontact it finds and verifies in one step and charges only when a verified email comes back, and it adds a credit refund if the bounce rate on its emails goes above 5%. Findymail is one of the providers in the [waterfall email enrichment](https://frontal.so/gtm-apis/stacks/waterfall-enrichment) and [hiring signal to outbound](https://frontal.so/gtm-apis/stacks/hiring-signal) stacks on this site, where the cost is worked out end to end. ## Before you build against it Five things to settle first, each one read off Findymail's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration. Provenance ## Where the data comes from, and what you may do with it The question that arrives late and expensively is who is allowed to hold the data. These are the fields it returns, the coverage it claims and the compliance it publishes. | Provider | Fields returned | Coverage | Compliance | Redistribution | | --- | --- | --- | --- | --- | | [Findymail](https://frontal.so/gtm-apis/enrichment-apis/findymail-api-review) | Work email, Mobile phone, LinkedIn profile, Firmographics, Technographics | Strongest in EMEA | GDPR DPA | Not stated | Findymail states no redistribution position on its pricing or docs pages. Internally that never matters. Put the rows in something your customers can see and it becomes the question your legal team asks first. Two practical notes. A compliance badge describes the vendor rather than your use of it, so a GDPR DPA does not give you a lawful basis for the outreach you send. And the vendor runs its own opt-out, which means a person who asks you to delete their record has to be removed from your copy as well as from theirs. ## If Findymail is not the answer Four providers in the [Enrichment APIs](https://frontal.so/gtm-apis/enrichment-apis) listing that solve the same problem differently. Each one is a trade, and the trade is named. [Prospeo $49/mo Half the entry price, also EMEA-strong, and it does sell EU mobile numbers. The direct replacement when the missing field is the problem.](https://frontal.so/gtm-apis/enrichment-apis/prospeo-api-review) [LeadMagic $99/mo Mobile at 5 credits against 10, a published cost for every operation, and unused credits that carry over up to twice the monthly allotment.](https://frontal.so/gtm-apis/enrichment-apis/leadmagic-api-review) [FullEnrich $29/mo 25 sources in one call, plus personal emails, which Findymail does not sell. Costs 2.8 times more per work email.](https://frontal.so/gtm-apis/enrichment-apis/fullenrich-api-review) [Apollo $49/seat/mo Within one percent per credit, with sourcing and sending included, at the cost of a seat license and thinner European coverage.](https://frontal.so/gtm-apis/enrichment-apis/apollo-api-review) The full set, organized by the reason people leave, is on the [Findymail alternatives](https://frontal.so/gtm-apis/alternatives/findymail-alternatives) page. ## Findymail against the obvious rival Same rate cards, read side by side, with the arithmetic done on a worked volume rather than left to you: [LeadMagic vs Findymail](https://frontal.so/gtm-apis/compare/leadmagic-vs-findymail), [Findymail vs Prospeo](https://frontal.so/gtm-apis/compare/findymail-vs-prospeo) and [Findymail vs Hunter](https://frontal.so/gtm-apis/compare/findymail-vs-hunter). The same again, against the rest of the field: [FullEnrich vs Findymail](https://frontal.so/gtm-apis/compare/fullenrich-vs-findymail) and [Findymail vs Smartlead](https://frontal.so/gtm-apis/compare/findymail-vs-smartlead). Every pairing in the directory is on the [compare hub](https://frontal.so/gtm-apis/compare). [LeadMagic vs Findymail Compare A published per-operation rate card against a refundable bounce guarantee.](https://frontal.so/gtm-apis/compare/leadmagic-vs-findymail) [Findymail vs Prospeo Compare Two EMEA-strong indexes, fifty dollars apart on the entry plan.](https://frontal.so/gtm-apis/compare/findymail-vs-prospeo) [Findymail vs Hunter Compare A refundable bounce guarantee against the best-documented starter in the category.](https://frontal.so/gtm-apis/compare/findymail-vs-hunter) ## Calling these APIs one by one? *Run them from one Clay table.* Clay runs a waterfall across 150+ data providers from one table, without a separate contract with each. A lookup that finds nothing costs no data credit, and the free plan includes 500 actions a month. [Try Clay](https://go.frontal.so/clay) [See the Findymail alternatives](https://frontal.so/gtm-apis/alternatives/findymail-alternatives) Frontal is a Clay Elite Studio Partner. What practitioners say ## What Findymail users say, in their own words The one part of this page that is not a vendor claim. The comment below makes its point in crude words, so we summarize it in our own words and link the thread. A Reddit claim is a signal rather than a fact, so nothing here is the only source for a figure on this page. ### Run the bake-off yourself, because the answer is list-specific **In our words:** Asked which email finder to buy, a seller answers that the tools are much the same, and that an hour spent trying each one's free credits on a few real prospects settles it better than any recommendation. [r/sales](https://www.reddit.com/r/sales/comments/1ja7u35/what_is_the_best_email_finder_tool/) · March 2025 · summarized rather than quoted The same conclusion this page reaches. Match rate is a property of your list, not of a vendor, so the only number that decides this is the one you measure on your own rows. Every provider on this page except LeadMagic has a free tier or a trial you can run that test on. The thread it comes from is also the clearest example of why these blocks are scoped the way they are: it is a "best email finder" question, and most of the replies are people naming the tool they sell. The one worth reading is the one that tells you not to trust any of them. 14 threads read on 13 October 2026, searched by vendor name. Scores and dates are the comment's own. Nothing here is the only source for a price or a limit on this site: every figure in the tables above comes from a vendor's own page. FAQ ## Findymail API, answered **Is the Findymail API free?** No. A free account with 10 credits and no card, which this directory counts as a trial rather than a free tier. Paid plans start at $99/mo. **How much does the Findymail API cost?** Findymail starts at $99/mo. Its unit rate is $0.0198 per credit. It bills by subscription or by credit pack. Read from Findymail's own pricing page on 24 October 2026. **What are the Findymail API rate limits?** Concurrency, not rate: 300 simultaneous requests by default, 25, 50 or 150 per team on Individual, Team and Scale; the credit plan's figure is not stated. **How do I get a Findymail API key?** A Findymail API key is created on the API tokens page of the app, and Findymail lists API access as free on all plans. Requests authenticate with bearer token. The current steps are in Findymail's own documentation, which is authoritative on anything that has changed since 24 October 2026. **Does Findymail have an MCP server?** Yes. MCP access listed on every plan, for Claude and ChatGPT; no server address is documented. It is listed with the others on the MCP page. Published by ## [Frontal](https://frontal.so/) Frontal is the go-to-market partner for B2B tech companies past product-market fit. It publishes this directory. Every price, tier requirement and rate limit on this page was read from the vendor's own pricing page, developer documentation or knowledge base on the date below. Nothing on it is restated from a press release or a third-party listing. Where a vendor publishes no public figure, this page says so rather than estimating. [How we checked](https://frontal.so/gtm-apis#method). Reviewed by [Kenny Damian](https://www.linkedin.com/in/kenny-damian-90aba221a/) Co-founder & Head of GTM, Frontal **Verified** 24 Oct 2026 **Sources** 2 vendor documents Read from - [findymail.com/pricing](https://www.findymail.com/pricing) - [app.findymail.com/docs](https://app.findymail.com/docs/)