CUFinder data enrichment APIs have grown faster than most people realize: the catalogue now holds 31 endpoints.
And I’ll be honest with you. Even people on our own team lose track of what’s in there.
So I built the map I kept wishing existed. Every endpoint on one page: what goes in, what comes out, what it costs in credits, and where its documentation lives.
This isn’t a sales pitch. It’s a directory. Skim the quick-reference table, jump to your group, and follow the docs link when you’re ready to call something.
Let’s get into it.
30-Second Summary
CUFinder offers 31 data enrichment API endpoints, grouped on this page into six families: enrichment, finders, search and discovery, company intelligence, normalizers, and checkers.
What you’ll find below:
- All 31 endpoints with their inputs, outputs, and who each one is for
- The documented credit cost of every endpoint, from 0 to 10
- A verified Python example using the official SDK
- Authentication, rate limits, and error handling in plain words
- An honest section on where CUFinder fits (and where it doesn’t)
Every description on this page was checked against the endpoint’s own documentation in August 2026. Where I state a number, the sentence links the docs page that states it.
Let’s go 👇
What Are CUFinder Data Enrichment APIs?
CUFinder’s data enrichment APIs are REST endpoints that turn one identifier into verified company or contact data.
You send a company name, a domain, an email address, or a LinkedIn URL. The API matches it against a database of 1B+ person profiles and 85M+ companies, and sends back structured JSON.
That’s what “enrichment” means here: completing a record you already hold. You bring the fragment. The endpoint brings the rest.
And here’s the mental model that makes the whole catalogue click: every endpoint is keyed by its INPUT, not its output. Two endpoints can return similar fields. What separates them is what you must be holding to make the call.
All 31 endpoints share the same mechanics:
- One base URL →
https://api.cufinder.io/v2 - One authentication method → an API key sent with each request
- One response shape → JSON with
status,data, and your remainingcredit_count - One billing unit → credits, consumed per record found
Learn one endpoint and you’ve basically learned all 31. The only real question is which ones your workflow needs.
Match quality does vary by endpoint and region, which is why each docs page publishes its own confidence figures. I’d rather point you at those numbers than average them into something tidy.
How This Directory Is Organized
I’ve sorted the 31 endpoints into six groups:
- Enrichment APIs → complete a record you already hold
- Finder APIs → hunt one missing field
- Search and discovery APIs → pull new records from filters
- Company intelligence APIs → answer one narrow question about a company
- Normalizer APIs → clean the fields you have
- Checker APIs → classify a company in or out of your market
Workflow-level recipes (full builds with code) live over on our API hub. This page stays at the catalogue level on purpose. And if this page and a docs page ever disagree, trust the docs. They’re the living source.
Which Endpoint Fits the Data You’re Holding?
Start from the identifier you already hold. It narrows 31 endpoints down to two or three.
That’s the whole trick. Not “which API is best,” but “what’s sitting in my spreadsheet right now?”
| You have | You want | Call this |
|---|---|---|
| A company name | Its website domain | Company Name to Domain |
| A domain | The registered company name | Domain to Company Name |
| A person’s name + employer | Their full contact record | Person Enrichment |
| An email address | The person behind it | Reverse Email Lookup |
| A LinkedIn profile URL | A verified work email | LinkedIn Profile Email Finder |
| An ICP filter set | A list of matching companies | Company Search |
| A people filter set | A list of matching contacts | Person Search |
| Hiring-related filters | Live job postings + firmographics | Jobs API |
| Messy names, phones, addresses | Clean, standardized fields | The three normalizers |
| A domain | A SaaS or B2B/B2C classification | The two checkers |
Now let’s walk the full catalogue, group by group.
Enrichment APIs: Complete a Record You Already Hold
These four are the workhorses. Each takes one identifier and fills in the rest of the profile.
1. Company Enrichment API
Give the Company Enrichment API a company name, domain, or LinkedIn URL. Back comes the full business profile: industry, revenue, headcount, contact info, and tech stack (15+ verified data points, per its docs).
One request instead of eight. Its docs list the cost at 4 credits per record found, and it’s my default whenever a new account lands in the CRM. Lead qualification, account intelligence, half-empty rows: this is the endpoint that handles them.
2. Person Enrichment API
Feed the Person Enrichment API a full name plus a company name. It returns the complete contact record: job title, email, phone, LinkedIn URL, and location.
At a documented 10 credits per record found, it’s the priciest endpoint in the catalogue. It’s also the one that returns the most per person. Built for lead completion.
3. LinkedIn Profile Enrichment API
You paste a LinkedIn profile URL into the LinkedIn Profile Enrichment API. It hands back the person’s name, title, employer, location, and social profiles, plus their company’s details.
At 1 credit per record found, it’s a cheap way to turn Sales Navigator exports or candidate lists into real records. Recruiting screens and CRM personalization are its documented home turf.
4. Reverse Email Lookup API
The Reverse Email Lookup API starts from nothing but an email address. It returns the person behind it: full name, job title, LinkedIn, employer, and location.
Perfect for form fills and newsletter signups where email was the only field you captured. Documented at 4 credits per record found. Its docs pitch it for identity resolution and lead validation, and that’s exactly where I reach for it.
Finder APIs: Hunt One Specific Field
Six endpoints, each chasing exactly one missing value. Small inputs, small outputs, small costs.
5. Company Email Finder API
Point the Company Email Finder API at a company website and it returns up to five verified role-based emails. Think info@, contact@, and support@.
When you’re reaching small businesses, a working shared inbox often matters more than a named contact. Costs 1 credit per record found. The docs list CRM completion, outreach automation, and support workflows as its target jobs.
6. Company Phone Finder API
The Company Phone Finder API takes a company name and returns up to two verified business phone numbers, documented at 2 credits per record found.
It’s the switchboard fallback: when no direct dial exists for a contact, a verified main line still gets your SDR to the right department.
7. LinkedIn Profile Email Finder API
Hand the LinkedIn Profile Email Finder API a profile URL and it returns that person’s verified business email. The match comes from the 1B+ contact database, not a guessed pattern.
This is the bridge from LinkedIn prospecting to email outreach. Documented at 5 credits per record found.
8. LinkedIn Company URL Finder API
Give the LinkedIn Company URL Finder API a company name or domain. It returns the verified LinkedIn company page URL at 3 credits per record found.
Useful anywhere your workflow needs the LinkedIn page as a key: research automation, CRM enrichment, or monitoring lists.
9. Company Name to Domain API
The Company Name to Domain API converts a company name (with an optional country code) into the official website domain, with a confidence score attached. Its docs state 94-98% accuracy.
At 1 credit per record found, it’s usually the first call in any cleanup chain. Trade-show lists and CRM exports full of bare names start here.
10. Domain to Company Name API
Running the other direction, the Domain to Company Name API turns a website URL into the registered company name for 1 credit per record found.
It shines in visitor identification and attribution work, where all you’ve got is a pile of domains from your analytics tool.
Search and Discovery APIs: Find Records You Don’t Have Yet
Enrichment completes what you hold. These seven endpoints discover what you don’t. You send filters, they send back new records.
11. Company Search API
The Company Search API queries the 85M+ company index with 16 stackable filters: location, industry, employee size, founding year, funding raised, revenue range, and more.
You describe your ICP, it returns the matching companies at 3 credits per record found. This is list-building from zero. And each match arrives with real profile fields, so scoring can start the moment results land.
12. Person Search API
Its sibling, the Person Search API, runs combined filters across 1B+ professional profiles. Filters cover job title role and level, geography, and a full set of company attributes.
Back come matching people with titles, social profiles, and employer details, at 5 credits per record found. Built for precision prospecting and executive search.
13. Jobs API
The Jobs API returns live job postings that match your filters. Each posting arrives enriched with the hiring company’s full firmographics, the descriptive company facts like size, industry, and revenue.
Note the different billing unit here: its docs state 2 credits per search, not per record. Hiring activity is one of the best timing signals in B2B, and this endpoint is how you tap it programmatically. It was built for sourcing tools, talent-intelligence platforms, and hiring-signal workflows.
14. Local Business Search API
For the neighborhood layer of the economy, there’s the Local Business Search API. It queries local businesses by name, location, and industry. Results carry phones, emails, ratings, social profiles, and NAICS industry codes, with Google Maps data attached.
Traditional B2B databases mostly skip these businesses. Documented at 5 credits per record found.
15. Company Lookalikes Finder API
Show the Company Lookalikes Finder API one company and it returns a curated list of similar ones. Matches run on industry, size, and characteristics, with profiles included.
Feed it your best customers and you get your next target accounts. Costs 5 credits per record found. Returned profiles carry employee counts, revenue estimates, and contact details, per the docs.
16. Company Employee Finder API
The Company Employee Finder API takes a company name and returns a paginated list of verified employees. Each record carries a job title, department, seniority level, and LinkedIn URL.
That’s org-chart mapping and buying-committee targeting in one endpoint, at 2 credits per record found.
17. B2B Customers Finder API
Here’s a rare one. The B2B Customers Finder API takes a company’s domain and returns verified business customers of that company, with profiles and relationship indicators.
Point it at a competitor and you’re looking at their customer base: competitive whitespace, mapped for 3 credits per record found.
Company Intelligence APIs: One Narrow Question, Answered
Nine endpoints, each built to answer a single specific question about a company. You could pull most of this from full enrichment. But when you only need one field, why pay for fifteen?
18. Company Fundraising API
The Company Fundraising API answers “who funded them, and when?” It returns funding rounds, raised amounts, and investor names for 4 credits per record found.
Freshly funded companies hire, expand, and buy. Timing outreach around that is a classic play.
19. Company Revenue Finder API
Ask the Company Revenue Finder API about a company and it returns an annual revenue estimate at 3 credits per record found.
Revenue is the backbone of most lead-scoring and segmentation models, so this one earns its keep in routing logic.
20. Company Tech Stack Finder API
The Company Tech Stack Finder API lists the technologies a company runs, from CMS platforms to analytics tools, for 3 credits per record found.
Selling a Salesforce integration? You only want companies on Salesforce. I’ve written up full technographic data API workflows separately if you want the deep version.
21. Company Subsidiaries Finder API
For enterprise account planning, the Company Subsidiaries Finder API returns the child companies and divisions under a parent, at 3 credits per record found.
Knowing the full corporate family stops you from prospecting the same organization five times under five names.
22. Company Employee Count API
The Company Employee Count API breaks a company’s headcount down by country, for 1 credit per record found.
Territory planning teams love this one: it shows not just how big a company is, but where its people actually sit.
23. Company Locations API
Its neighbor, the Company Locations API, returns verified business addresses at 2 credits per record found. You get country, state, city, postal code, and street.
Field sales routes and regional targeting start with addresses you can trust.
24. Company Mission Statement API
An unusual and honestly underrated one. The Company Mission Statement API extracts a company’s mission statement from its domain. Back comes the full text with a source URL, at 3 credits per record found.
Outreach that echoes a prospect’s own stated priorities reads very differently from a template.
25. Company Snapshot API
The Company Snapshot API goes a level deeper: from a domain, it extracts who the company sells to. That means ICP characteristics, target industries, buyer personas, and core value propositions, with supporting evidence.
Battlecards and pitch prep, automated. Documented at 3 credits per record found.
26. Company Career Page Finder API
Recruiting tools use the Company Career Page Finder API to pull a company’s career page URL from its domain. It covers ATS-hosted pages and job-board variants, at 3 credits per record found.
Where a company posts roles tells you a lot about how it hires.
Normalizer APIs: Clean What You Already Have
Nobody gets excited about normalizers. Then their match rates double. These three fix the messy fields that quietly ruin enrichment runs.
27. Company Name Normalizer API
The Company Name Normalizer API standardizes messy company names. It fixes capitalization and stray spaces so “ACME corp ” and “acme Corp.” stop living as two records.
And here’s the part I love: its docs list the cost at 0 credits. It’s free.
💡 Tip: The Company Name Normalizer costs 0 credits. Run it across your whole list BEFORE you spend anything on enrichment: clean names in, better match rates out.
28. Phone Number Normalizer API
The Phone Number Normalizer API converts phone numbers into E.164, the international numbering format standardized by the ITU. Country codes and validity flags come with it, for 1 credit per record found.
Dialers and SMS tools expect E.164. Your CRM full of “(030) 12 34 56” does not deliver it.
29. Address Normalizer API
Rounding out the trio, the Address Normalizer API standardizes physical addresses into USPS-compliant and international postal formats. You get parsed components and a validation status, at 1 credit per record found.
Deduplication, territory assignment, and shipping all get easier when addresses agree with themselves.
Checker APIs: Yes-or-No Answers About a Company
Two endpoints for one job: filtering companies in or out of your addressable market before you spend real credits on them.
30. Company SaaS Checker API
The Company SaaS Checker API analyzes a domain and tells you whether the company runs a SaaS business model. A confidence score and supporting indicators ride along, at 2 credits per record found.
If your product only makes sense for software companies, this check saves whole campaigns from bad targeting.
31. Company B2B or B2C Checker API
And number 31: the Company B2B or B2C Checker API classifies whether a company sells to businesses or consumers. Mixed-model indicators come included, for 3 credits per record found.
Simple label, big consequences: your whole routing and messaging logic can hang off this one field.
That’s all 31. And a quick note on method, because trust matters on a page like this: every card above was written against the endpoint’s own documentation, and every card links it. Where the docs state a number (credits, limits, accuracy), I quoted it. Where they don’t, I didn’t.
What a Call Actually Looks Like
So what does calling one of these actually look like? Less than you’d think.
There are official SDKs in five languages (Python, TypeScript, Go, Rust, and Ruby), all wrapping the same base URL, https://api.cufinder.io/v2.
Here’s the Python version, exactly as the docs show it:
from cufinder import Cufinder
client = Cufinder('your-api-key-here')
# Person Enrichment: name + company in, full contact record out
person = client.tep('iain mckenzie', 'stripe')
# Company Enrichment: one identifier in, full company profile out
company = client.enc('cufinder')
print(person)
print(company)Every response follows the same shape. You get a status flag, a data object holding the matched record with its confidence level, and a credit_count showing your remaining balance.
Here’s the documented response for that person call, trimmed to the interesting fields:
{
"status": 1,
"data": {
"confidence_level": 97,
"query": "iain mckenzie at stripe",
"person": {
"full_name": "iain mckenzie",
"job_title": "engineering",
"linkedin_url": "linkedin.com/in/iain-mckenzie",
"company_name": "stripe",
"company_website": "https://stripe.com",
"email": "iain.mckenzie@stripe.com"
},
"credit_count": 9761
}
}No response-parsing surprises between endpoints. Swap tep for another endpoint’s method and your plumbing stays the same.
Authentication, Rate Limits, and Errors
Three pieces of machinery sit under every call. Here’s each one, straight from the docs.
Authentication. Every request carries an API key generated from your CUFinder dashboard. The authentication guide walks through it. One key, no OAuth dance, no token rotation.
Rate limits. The documented limit is 100 requests per minute per key, on a fixed-window strategy. That means the counter resets every 60 seconds rather than sliding continuously. Space your batch jobs accordingly.
Errors. Failed requests return one of two documented error types: api_error (the platform’s fault, rare) and invalid_request (your fault, common). The docs say so themselves, and fair enough. Standard HTTP status codes ride along, so your usual retry logic applies.
How the Credit System Works
Every endpoint’s documentation states its own credit cost, and the range across the catalogue runs from 0 to 10 credits per record found.
That phrase, per record found, is the important part. A lookup that comes back empty doesn’t bill you.
🧠 Remember: Credits are consumed per record FOUND. A no-match lookup costs nothing, so testing an ugly list won't drain your balance the way per-request billing would.
Here’s a sample of documented costs across the range, so you can feel the shape:
| Endpoint | Documented credit cost |
|---|---|
| Company Name Normalizer | 0 (free) |
| Company Name to Domain | 1 per record found |
| Company Email Finder | 1 per record found |
| Company Employee Finder | 2 per record found |
| Jobs API | 2 per search |
| Company Search | 3 per record found |
| Company Enrichment | 4 per record found |
| LinkedIn Profile Email Finder | 5 per record found |
| Person Enrichment | 10 per record found |
Estimating a job’s cost before you run it takes one line of arithmetic:
🔍 Formula: → estimated credits = rows × endpoint cost × expected match rate. A 1,000-row list through Company Enrichment (4 credits) at an 80% match rate → about 3,200 credits.
Your remaining balance comes back in every response as credit_count, so monitoring spend is just reading the field you already receive.
One quirk worth flagging: the Jobs API is the only endpoint billed per search rather than per record found. Factor that in when you estimate a signal-monitoring job.
I’m deliberately not quoting dollar prices here. Plans change, and this page is about the catalogue. For how credit and per-record models compare across vendors, I’ve broken down what data enrichment APIs cost across the market separately.
How I Chain These Endpoints
That’s the catalogue. Here’s the machinery in motion. Single endpoints are useful, but chains are where the real work happens.
Pattern 1: CRM autofill. A form submission arrives with just an email. Reverse Email Lookup identifies the person, Company Enrichment fills in their employer, and the CRM record is complete before a rep ever opens it. Trigger it from a webhook and it runs itself.
Pattern 2: prospect list from zero. Company Search (or Lookalikes, seeded with your best customers) builds the account list. Next, the Employee Finder surfaces the right people at each account. LinkedIn Profile Email Finder gets you their verified emails. I’ve written the full walkthrough of how to build a prospect list with a company data API if you want every step.
Pattern 3: hiring signals. The Jobs API flags companies hiring for roles your product serves, and Company Enrichment turns each hit into a scored account. My hiring-signals workflow covers this one end to end.
Pattern 4: competitive research. The B2B Customers Finder maps who buys from a competitor. Then the Tech Stack Finder shows what those companies already run. Together, they hand you a displacement list with enough context to write specific, honest outreach instead of guesswork.
📌 Example: The cleanup chain that fixes most messy lists → Company Name Normalizer (free) → Company Name to Domain (1 credit) → Company Enrichment (4 credits). Normalize, resolve, THEN enrich.
That last chain? I learned it the embarrassing way.
Web Summit, Lisbon, November 2021. I came home with about 1,400 scanned badges: company names only, typed by tired booth staff, mine included. “stripe payments,” “Stripe Inc,” “STRIPE.” You get the idea.
I fed the raw list straight into the enrichment endpoint. The match rate that came back was bad enough that our sales lead asked, in the team call, whether the data vendor was broken. It wasn’t. My inputs were.
The worst part? The fix had been sitting in the catalogue the whole time. For free.
So I reran the whole thing: normalizer first, then name-to-domain, then enrichment on clean domains. Most of the list came back on the second pass. That chain order has been my default ever since. The order you call endpoints in matters as much as which endpoints you call.
One honest note before you automate any of this: enriched contact records are personal data. If you operate in Europe, processing them needs a lawful basis under the GDPR. Build that check into the workflow, not around it.
How to Run a Fair 200-Row Test
Marketing pages won’t settle whether a data API fits your stack. Your own rows will. So before you commit to any vendor (ours included), run the same small test.
Here’s the version I give every team that asks:
- Pull 200 rows from YOUR CRM, not a demo file, and keep the ugly ones in
- Run the free Company Name Normalizer first, so you test the data instead of the typos
- Enrich, then measure two things separately: match rate (how many came back) and field accuracy (hand-check 30 records against LinkedIn and company sites)
- Note
credit_countbefore and after: that difference, divided by usable records, is your true cost per record
Two hundred rows takes an afternoon. And it ends more vendor debates than any comparison table I’ve ever built.
Where CUFinder Fits (and Where It Doesn’t)
This is our product, so read this section knowing that. But I’d rather you test with accurate expectations than churn with inflated ones.
Where it fits well:
- Narrow endpoints most suites skip: mission statements, subsidiaries, SaaS checks, B2B customer mapping
- The per-record-found billing model, which makes testing messy lists cheap
- Self-serve access: you can call an endpoint today without talking to sales
Where it doesn’t:
- Coverage depth varies by region and company size. The 85M+ index is wide, but very small local firms outside major markets will match less often, so test with your own geography before committing
- There’s no buyer-intent data in this catalogue. If third-party intent signals anchor your motion, you’ll pair CUFinder with something else
- The API bills per call, which suits pipelines and products. For a big one-off CSV job, the dashboard’s file-upload flow is the better tool than writing throwaway code
And if you’re still at the comparison stage, start with my honest rundown of the best data enrichment APIs. CUFinder is in it, but so are the alternatives, with their real strengths named.
Weigh those trade-offs against your actual workflow, then let the 200-row test above make the final call.
Frequently Asked Questions
What is the CUFinder API?
The CUFinder API is a set of 31 REST endpoints for enriching, finding, searching, and cleaning B2B data.
All endpoints live under one base URL, authenticate with one API key, and return the same JSON response shape. They draw on a database of 1B+ person profiles and 85M+ companies.
How many data enrichment APIs does CUFinder offer?
Thirty-one endpoints, as of August 2026.
They break into six groups: four enrichment APIs, six finders, seven search and discovery APIs, nine company intelligence APIs, three normalizers, and two checkers. Every one is listed above with its docs link.
Where is the CUFinder API documentation?
The full technical documentation lives at apidoc.cufinder.io.
Each endpoint has its own page there with request attributes, a sample response, and SDK snippets in five languages. Every entry in this directory links to its matching docs page.
How does CUFinder’s credit system work?
Each endpoint consumes a documented number of credits per record found, ranging from 0 to 10.
Cheap lookups like Company Name to Domain cost 1 credit. The heavyweight Person Enrichment costs 10. And the Company Name Normalizer costs nothing at all, with your balance returned in every response as credit_count.
Do failed lookups consume credits?
No. The documented billing unit is “per record found,” so a lookup that matches nothing costs nothing.
That matters more than it sounds. It means a low-quality input list wastes your time but not your balance, and it changes how freely you can experiment.
What is the CUFinder API rate limit?
The documented limit is 100 requests per minute per API key, enforced with a fixed-window strategy.
In practice, that’s 100 calls inside any 60-second window before requests start getting rejected. Batch jobs should pace themselves against that window. The usage limits page has the details.
Which languages have official CUFinder SDKs?
TypeScript, Python, Go, Rust, and Ruby all have official SDKs on GitHub.
And the endpoints are plain REST with JSON responses. So any language that can send an HTTP request works without an SDK: PHP, Java, even a spreadsheet script.
Can I integrate CUFinder APIs with my CRM?
Yes: through your CRM’s workflow builder, custom code actions, or middleware.
The common pattern: the CRM fires a webhook when a record is created. Your middleware calls the relevant endpoints, and the enriched fields get written back. No special connector required, because it’s all standard HTTP.
What’s the difference between the enrichment and search endpoints?
Enrichment completes a record you already hold; search discovers records you don’t have yet.
If you’re holding an identifier (a name, email, domain, or LinkedIn URL), you want an enrichment or finder endpoint. But when what you hold is criteria, like “marketing directors at German SaaS companies,” you want Company Search, Person Search, or the Jobs API.
It’s Time to Pick Your Endpoint
Thirty-one endpoints. Six groups. One question: what data are you holding, and what’s missing from it?
Answer that, and this directory hands you the two or three endpoints worth testing. Start small. A couple hundred rows tells you more than any page of mine can, this one included.
The full documentation is where I’d go next. You could have your first call returning JSON before your coffee cools.
So tell me, which of the 31 will you call first?
Bad
Okay
Good
Amazing
