The CUFinder API is a set of 31 REST endpoints for enriching, searching, and cleaning B2B data. Each one does a single job. You send an identifier such as a company name, a domain, an email, or a LinkedIn URL, and you get back structured JSON you can write straight into your database. That’s what a B2B data API is, reduced to its honest core: identifiers in, structured business facts out.
This page is the directory. I have grouped every endpoint by the job it does rather than by alphabetical order, because that is how you actually pick one. Each entry shows what you send, what comes back, what it costs in credits, and links to the full reference with request and response examples.
Use it in two passes. First skim the group headings to find the job you need done. Then read that group’s table left to right (input, output, cost) and click through to the reference only when you have a real candidate. Five minutes here saves an afternoon of trial calls.
Before your first request
Four things are worth knowing before you start. They apply to every endpoint in the list below.
- Authentication. Every request needs an API key. See Authentication for how to pass it, and Quick Start for a working first call.
- Rate limits. Keys are limited to 100 requests per minute using a fixed window. So you can burst 100 calls at any point inside a 60 second window. Details in Usage Limits.
- Failure handling. Responses return standard HTTP codes with a JSON body. Read Status Codes and Errors before you write retry logic, because a 404 and a 429 need very different handling.
- SDKs. Official client libraries exist in five languages (TypeScript, Python, Go, Ruby, and Rust), and every endpoint reference page carries ready-to-run examples in each. Method names stay identical across languages.
📌 A note on credits: a lookup that returns no match generally does not cost you. But repeated identical inputs in one file do get charged separately, because nothing you upload is stored. Deduplicate before you send.
A credit, throughout this page, is the unit your plan meters: each table below shows the documented cost per record found, so you can price a pipeline before you build it.
Company enrichment and profiles
These take a company identifier and return attributes about that company. Start with Company Enrichment if you want everything at once, then use the narrower endpoints when you only need one field and want to spend fewer credits.
| Endpoint | You send | You get back | Credits |
|---|---|---|---|
| Company Enrichment | Company name or domain | Full profile: industry, size, headcount, location, description | 4 |
| Company Revenue Finder | Company name or domain | Annual revenue, 96% confidence | 3 |
| Company Employee Count | Company name or domain | Headcount broken down by country, 98% confidence | 1 |
| Company Locations | Company query | Country, state, city, postal code, street, 95% confidence | 2 |
| Company Snapshot | Company domain | ICP characteristics, target industries, buyer personas | 3 |
| Company Mission Statement | Company domain | Mission text with source URLs | 3 |
Company search and discovery
Use these when you do not have a list yet. Instead of enriching a company you already know, you describe the kind of company you want and get matches back.
| Endpoint | You send | You get back | Credits |
|---|---|---|---|
| Company Search | Filters: location, industry, employee size, funding, founding year | Matching company records | 3 |
| Company Lookalikes Finder | A target company | Companies matching its industry, size, and profile | 5 |
| B2B Customers Finder | A target company domain | Verified business customers of that company | 3 |
| Company Subsidiaries Finder | Parent company | Child companies and divisions | 3 |
| Local Business Search | Location and industry | Local businesses with phones, emails, ratings, socials, 95% confidence | 5 |
Company classification
These answer yes or no questions about a company. They are cheap qualification filters, so run them early in a pipeline to drop records before you spend credits enriching them. The credits column below is the whole argument.
| Endpoint | You send | You get back | Credits |
|---|---|---|---|
| B2B or B2C Checker | Company domain | Whether it sells to businesses or consumers | 3 |
| SaaS Checker | Company domain | Whether it runs a SaaS business model | 2 |
| Tech Stack Finder | Company name or domain | Technologies in use, from CMS to analytics tools | 3 |
Identifier resolution
Most enrichment pipelines break because the input identifier is wrong, not because the data is missing. These three convert one identifier into another so the rest of your calls actually match.
| Endpoint | You send | You get back | Credits |
|---|---|---|---|
| Company Name to Domain | Company name | Verified website URL, 94 to 98% accuracy | 1 |
| Domain to Company Name | Website URL | Registered company name, 97% confidence | 1 |
| LinkedIn Company URL Finder | Company name or domain | Verified LinkedIn company URL, 96% confidence | 3 |
Contact and person data
This is the largest group, because there are many ways to arrive at a person. Pick the endpoint that matches the identifier you already hold rather than the one that sounds closest to your goal.
| Endpoint | You send | You get back | Credits |
|---|---|---|---|
| Person Enrichment | Full name plus company name | Job title, email, phone, and profile details | 10 |
| Person Search | Filters: name, company, location, industry, revenue | Matching contact records | 5 |
| Reverse Email Lookup | Email address | Full name, job title, LinkedIn, company data | 4 |
| LinkedIn Profile Enrichment | LinkedIn profile URL | Person and company information | 1 |
| LinkedIn Profile Email Finder | LinkedIn profile URL | Verified business email, 94% confidence | 5 |
| Company Email Finder | Company name or domain | Up to five generic company emails such as info@ or support@ | 1 |
| Company Phone Finder | Company name, domain, or LinkedIn URL | Up to two verified business phones, 93% confidence | 2 |
| Company Employee Finder | Company name | Employee records with job titles | 2 |
One distinction trips people up constantly. Company Email Finder returns role addresses that belong to the business, not to a person. If you need a specific human, use Person Enrichment, Reverse Email Lookup, or LinkedIn Profile Email Finder instead.
And notice the price spread in this group. Enriching from a LinkedIn URL costs 1 credit while enriching from a name and company costs 10: same kind of output, very different price, decided entirely by which identifier you already hold. Route by identifier and the same pipeline gets dramatically cheaper.
Hiring and jobs
Job postings are public buying signals. A company hiring five sales reps is telling you something. These two endpoints read that signal.
| Endpoint | You send | You get back | Credits |
|---|---|---|---|
| Jobs API | Filters: job title, location, industry, company size, funding, revenue | Live job postings with the hiring company’s firmographics | 2 per search |
| Career Page Finder | Company domain | Career page URLs, job boards, application portals | 3 |
One billing note: the Jobs API charges per search rather than per record found, so a broad query costs the same as a narrow one.
Data hygiene
These do not add new information. Instead they make the data you already hold consistent, which matters because most match failures come from formatting rather than from missing records.
| Endpoint | You send | You get back | Credits |
|---|---|---|---|
| Address Normalizer | A messy address | USPS compliant and international formats with validation status | 1 |
| Phone Number Normalizer | A phone number in any format | E.164 format with country code, area code, validation status | 1 |
| Company Name Normalizer | Inconsistent company names | Standardized capitalization with extra spacing removed | 0 |
Yes, that last row says zero. Company Name Normalizer is free to run, so run it on everything before you match, because “ACME corp.” and “Acme Corporation” will not resolve the same way otherwise.
Funding
A category of one, but a useful one: funding rounds are timing signals, and this endpoint is the data source behind funding-triggered outreach.
| Endpoint | You send | You get back | Credits |
|---|---|---|---|
| Company Fundraising | Company name or domain | Funding rounds, amounts raised, investor details | 4 |
How the endpoints compose
The real power is in the chains, because each endpoint’s output is another endpoint’s input. Two examples of the shape:
Company name → Name to Domain (1) → Person Search 'cxo' (5) → Person Enrichment (10) Messy CRM row → Name Normalizer (0) → Company Enrichment (4) → B2B Checker (3)
Read the credit numbers in those chains and you can price a whole pipeline from this one page. That is exactly what the directory is for. The identifier you hold decides where a chain starts; the question you are answering decides where it ends. Everything in between is just routing.
Workflow guides
Single endpoints are easy. Chaining several of them to answer a real business question is where it gets interesting, so each guide below walks through one complete pipeline with runnable code.
- Find a CEO name from a business name and domain: resolve, search, enrich
- Build a targeted prospect list: company filters first, then the people inside
- Enrich LinkedIn URLs at scale: turn a dead URL column into contact records
- Build a lookalike account list: seed from your best customers
- Funding-triggered outreach: detect new rounds and time the pitch
- Track hiring signals: job postings as a public buying signal
- Clean a messy CRM export: normalize and deduplicate before you enrich
Integration guides and deep dives
Beyond the recipes, these longer guides cover single topics in depth: one endpoint family at a time, with the context and code the reference pages keep brief.
- Lead enrichment API: how it works and how to integrate one: the concepts behind enrichment pipelines
- Technographic data API: detecting a company’s tech stack at scale
- What is a company name-to-domain API?: the resolution step, explained with code
- Using a LinkedIn email finder API for lead generation: outreach patterns that scale
- Automating LinkedIn email finding with Python: from profile lists to email discovery
- CUFinder data enrichment APIs: the full guide: the whole suite in one walkthrough
Choosing a provider
If you are still evaluating rather than integrating, these cover the comparison side: what the categories mean, what things cost, and how CUFinder stacks up against the alternatives.
- B2B data API: what it returns and how to choose one: the four categories, and which you actually need
- Data enrichment API pricing: the models, the hidden costs, and cost per usable record
- The 9 best data enrichment APIs: tested and scored
- ZoomInfo API: access, pricing and alternatives
- Clearbit alternatives compared
How to choose the right endpoint
Work backwards from the identifier you hold, not from the answer you want. That single habit prevents most wasted credits.
- A company name only. Resolve it to a domain first, then enrich from there.
- A domain. Go straight to Company Enrichment, or to a narrower company endpoint.
- An email address. Reverse Email Lookup returns the person and their company in one call.
- A LinkedIn URL. Profile Enrichment gives you the whole profile, while Profile Email Finder returns just the address.
- Nothing yet. Start with Company Search or Person Search and build the list first.
Three habits save real money at volume. Run the cheap classification endpoints before the expensive enrichment ones, so you drop unqualified records early. Normalize your inputs before matching, because a name like “ACME corp.” and “Acme Corporation” will not resolve the same way. And check the credits column before you chain calls. The same answer often has a cheap path and an expensive one, and the difference compounds over every row in your file.
💡 Cheap-first rule: classification calls cost 2-3 credits; enrichment runs 4-10. Filter before you enrich and a 1,000-row pipeline gets dramatically cheaper.
Frequently asked questions
How many API endpoints does CUFinder have?
There are 31 endpoints in the standard REST suite, grouped into company data, contact data, search, classification, hiring, hygiene, and funding. The API reference holds the full specification for each one.
What is the API rate limit?
100 requests per minute per key, using a fixed 60 second window. If you exceed it you receive a 429 response, so build a backoff into your client rather than retrying immediately.
Which endpoint should I use to find someone’s email?
It depends on what you already have. From a LinkedIn URL use LinkedIn Profile Email Finder. Given a name and company instead, use Person Enrichment. Company Email Finder is different, because it returns generic role addresses rather than a specific person.
How much does each API call cost?
Credits per record found, ranging from 0 for the Company Name Normalizer to 10 for Person Enrichment. Every table on this page shows the documented cost next to its endpoint, so you can price a whole pipeline before writing it.
Do failed lookups cost credits?
A lookup that returns no match generally does not charge you. Duplicate inputs do get charged individually though, since uploaded data is not stored between requests. So deduplicate before sending a batch.
Is there an SDK?
Yes. There are official SDKs in five languages: TypeScript, Python, Go, Ruby, and Rust. Each endpoint reference includes ready to run examples in every one of them, so you can copy a working call rather than building the request by hand. Start with Quick Start.
Where to go next
If you are integrating for the first time, read Quick Start and make one live call before you design anything. Most integration problems show up in that first request, not later.
If you already know which data you need, jump straight to the endpoint reference from the tables above. And if you are chaining several endpoints together to answer a bigger question, start with the workflow guides. Each one is a complete, runnable pipeline built from the endpoints on this page.
Either way, the pattern stays the same: identifier in, structured JSON out, credits priced up front. Pick the endpoint that matches what you hold, and the rest of the integration is plumbing.
Bad
Okay
Good
Amazing
