Findymail API: Endpoints, Costs and Rate Limits Explained

The Findymail API is a JSON REST API at app.findymail.com that lets you find work emails (from name plus domain, or from a profile URL), verify emails, find phones, look up companies and tech stacks, run Intellimatch lead searches and check your credits. You authenticate with a Bearer token, and limits are based on how many requests run at once: 25, 50 or 150 simultaneous requests by plan, plus per-endpoint caps. As of November 2026, API access is included on every Findymail plan.

Some tool links here are affiliate links (disclosure). To get a token, create a Findymail account (free with 10 credits, no card). For the product as a whole, including pricing and accuracy claims, read our Findymail review.

Nerdy Joe is a certified Apollo.io Managed Services Partner and a PlusVibe Certified Silver Partner, and we are a Findymail affiliate. We did not call the API for this guide.

Everything below comes from Findymail's API documentation at app.findymail.com/docs, its API marketing page and its pricing page, checked November 9, 2026. Request examples are shown only in the shapes the docs show.

Findymail API quick facts

Authentication

Every request carries a Bearer token in the Authorization header. Findymail's docs say you retrieve the token by visiting the API tokens page in your account.

Authorization: Bearer {YOUR_AUTH_KEY}
Content-Type: application/json
Accept: application/json

Keep the token server-side. It draws on the same allowance as your team's web app and Chrome extension use, so a leaked token spends your usage or credits.

If you connect Findymail to other tools, create a separate token per tool. Findymail's Clay help article, for example, suggests creating a key named "Clay," which makes it easy to revoke one integration without breaking the rest.

Endpoint reference

These are the main endpoints in Findymail's API docs, with each endpoint's own concurrency cap and credit cost.

The domain search endpoint is marked deprecated in the docs. For "find the right people at this company" jobs, our suggestion is employees search or Intellimatch to get the people, then name search for the emails.

Example requests (as documented)

These are the request shapes from Findymail's docs. Replace the placeholder token and values with your own.

Find an email from name and domain

POST https://app.findymail.com/api/search/name
Authorization: Bearer {YOUR_AUTH_KEY}
Content-Type: application/json

{ "name": "John Doe", "domain": "website.com" }

The docs say domain takes a company domain (preferred) or a company name. The response includes a contact object with name, domain and email.

Find an email from a LinkedIn URL

POST https://app.findymail.com/api/search/business-profile
Authorization: Bearer {YOUR_AUTH_KEY}
Content-Type: application/json

{ "linkedin_url": "https://www.linkedin.com/in/johndoe" }

The docs accept a full profile URL or just the username. This endpoint has a lower concurrency cap (50) than name search (300), which matters for large batches.

Verify an email

curl --request POST "https://app.findymail.com/api/verify" \
  --header "Authorization: Bearer {YOUR_AUTH_KEY}" \
  --header "Content-Type: application/json" \
  --data '{"email": "user@example.com"}'

The response returns email, verified (true or false) and provider. It costs 1 verifier credit whatever the result.

Find a phone number

POST https://app.findymail.com/api/search/phone
Authorization: Bearer {YOUR_AUTH_KEY}
Content-Type: application/json

{ "linkedin_url": "https://www.linkedin.com/in/johndoe" }

The response has phone in E.164 format (or null) and line_type, for example "Mobile." The docs say the field is "Only available for US numbers" and that "requests for EU citizens will not return any result." Findymail's phone finder page describes phones more broadly as non-EU only.

Look up a company

POST https://app.findymail.com/api/search/company
Authorization: Bearer {YOUR_AUTH_KEY}
Content-Type: application/json

{
    "linkedin_url": "https://www.linkedin.com/company/findymail/",
    "domain": "stripe.com",
    "name": "Stripe"
}

That is the docs' example body, which shows all three fields. Each is optional on its own, but at least one is required (a 422 error says so if you send none). The response includes name, domain, company_size, industry, linkedin_url and description.

Check credits before a batch

GET https://app.findymail.com/api/credits?type=finder
Authorization: Bearer {YOUR_AUTH_KEY}

The response includes credits, verifier_credits (absent when one balance covers both), has_capacity (null on credit plans) and email. On usage plans, has_capacity is the field to check before you start a large job.

What the API costs

How you pay depends on which Findymail plan the token belongs to.

Findymail positions the credit plans as "the right fit if you resell Findymail data or embed it in your own product." The usage plans are for your own team, and Findymail does not publish how many lookups fit in each usage window.

Cost per result on the Starter credit plan

• Email found: $99 / 5,000 = about $0.0198 each. Misses are free.
• Phone found: 10 credits, about $0.198 each.
• Verification: 1 verifier credit per check, any result. The 5,000 bonus verifier credits cover emails from other sources.
• Rollover: unused credits roll over month to month, up to 2x your monthly allowance.

Findymail's terms add a fair-use clause: the absence of specific limits on usage plans "does not imply an unlimited consumption allowance." If you plan a very large API job on a usage plan, talk to Findymail first, or use a Findymail credit plan where each result has a fixed price. Our Findymail pricing guide covers every plan in detail.

Rate limits and how to handle 429s

Findymail's docs are clear on the model: "Most endpoints limit how many requests can run at the same time, not how many you send per minute." Two caps apply at once:

• Your plan's cap: 25 (Individual), 50 (Team) or 150 (Scale) simultaneous requests.
• The endpoint's cap: for example 300 for name search, verify, phone, reverse email and company; 50 for profile URL search, employees, Intellimatch and lookalike; 10 for the deprecated domain search.

The technology catalog search is the exception, with a limit of 10 requests per minute. Findymail's API marketing page mentions "300 concurrent requests by default"; the docs show 300 as a per-endpoint cap with lower plan caps on top, so the practical limit depends on plan and endpoint.

Requests over the limit get a 429 with error, retry_after (seconds) and retry_at (an ISO 8601 time). The docs' example message reads: "Your plan's usage capacity is reached for now. Retry after 2026-09-18T14:05:00+00:00 (in 300 seconds)."

Practical rules for a batch job (our recommendations, not Findymail's):

• Set your worker pool below the lower of your plan cap and the endpoint cap.
• On a 429, wait for retry_after instead of retrying immediately.
• Check has_capacity on /api/credits before starting a large run on a usage plan.
• Log 402 responses (not enough credits) and stop the job rather than looping.

Error codes

Async searches with webhook_url

Name search, profile URL search and the deprecated domain search accept an optional webhook_url. When you send one, the search runs asynchronously and the result is POSTed to your URL inside a payload object.

That is useful for large jobs where you do not want to hold connections open. The docs do not have a dedicated webhooks section, and they do not describe signing or retries, so validate incoming requests on your side.

Signal monitors (/api/signals/monitors) also accept an HTTPS webhook_url for delivered signals. The payload format for signals is not documented in what we read. Signal types in the docs are keyword_mention, new_hire, job_change, post_engagement and company_hiring, with each delivered signal costing 1 finder credit plus extras for filters and enrichment.

Common Findymail API use cases

Verify a list before it reaches your sequencer

Call /api/verify on each address and send only verified: true rows to your campaign. At 1 verifier credit per check whatever the result, this suits emails from other sources; Findymail says its own found emails are already verified (our Findymail review looks at that claim and its bounce guarantee). Our list of the best email verification tools compares dedicated verifiers if you need a second opinion.

Build your own email waterfall

Run name search first (higher concurrency), fall back to profile URL search when you have a LinkedIn URL, and only then try another provider. If you would rather not write that logic, Findymail is also a provider inside Clay; see our Findymail Clay integration guide.

Push found contacts into a cold email tool

Findymail lists native pushes to Instantly, Smartlead and lemlist, so you may not need code at all. For tools without a native integration, such as PlusVibe, chain the Findymail API with the sequencer's own add-lead API. Our Findymail to Instantly workflow shows both routes, and our cold email infrastructure guide covers the sending side.

Enrich CRM records

Call /api/search/company and /api/technologies on new accounts, and reverse email lookup on inbound leads. For ongoing enrichment of a whole CRM without code, Findymail sells Datacare, starting from $500 per month billed annually.

Feed AI agents

Findymail's pricing page lists MCP access, and its integrations page says you can connect Findymail to AI agents via Model Context Protocol. The setup article is in Findymail's help center; we did not review it.

No-code alternatives to the API

If you only need simple automations, Findymail's Zapier app has a New Contact trigger and two actions, Verify Email and Find Email (inputs Full Name and Domain). Findymail also links a Make app and a Google Sheets integration through an Apps Script formula.

What the docs do not cover

• Official SDKs (none mentioned).
• The contents of the OpenAPI spec and Postman collection (linked, not reviewed by us).
• The signal webhook payload format.
• Exact usage allowances per window on usage plans.
• Any webhook signing or retry behavior.

Final take

The Findymail API is straightforward: Bearer auth, small JSON bodies, clear credit costs, and a concurrency model you can design around. Its main limits are the plan caps on simultaneous requests and the unpublished usage allowances on non-credit plans.

For how the API fits with the rest of the product, read the full Findymail review. To start building, grab a token from a free Findymail account, test name search and verify on a few records, then pick a Findymail plan that matches your concurrency and volume.

Rather not build the list yourself?

Nerdy Joe is owned by Agency Growth Partners (AGP). AGP builds verified lead lists and runs outbound for agencies, including the enrichment and verification pipelines that would otherwise sit on this API. If you would rather hand it off, book a call with David.

Sources

• Findymail API docs: https://app.findymail.com/docs/
• Findymail API page: https://www.findymail.com/api/
• Findymail pricing: https://www.findymail.com/pricing/
• Findymail terms and conditions: https://www.findymail.com/terms-conditions/
• Findymail phone finder: https://www.findymail.com/phone-finder/
• Findymail email finder: https://www.findymail.com/lp/email-finder/
• Findymail integrations: https://www.findymail.com/integrations/
• Findymail CRM enrichment (Datacare): https://www.findymail.com/crm-enrichment/
• Findymail help center, How to use Findymail on Clay: https://help.findymail.com/en/article/how-to-use-findymail-on-clay-cafb59/
• Zapier, Findymail integrations: https://zapier.com/apps/findymail/integrations