Company data API: built for production workloads.
One request returns a full company record covering firmographics, headcount, technographics, funding, and web presence. Every match ships with a confidence score, and the strict-matching default keeps borderline results out of your production data.
What a company record contains
9 data categories, returned in one consistent JSON schema. Every company is keyed to a stable ID and its primary domain.
{
"id": "rc_c_9b21ee",
"name": "Stripe",
"domain": "stripe.com",
"linkedinUrl": "linkedin.com/company/stripe",
"logo": "https://…/stripe.png",
"industry": "Financial Software",
"specialties": ["Payments", "Billing", "Fraud"],
"employeeCount": 8400,
"employeeRange": "5001-10000",
"tagline": "Financial infrastructure for the internet",
"headquarters": { "city": "San Francisco", "country": "US" },
"locations": [ … 17 offices ],
"foundedYear": 2010,
"followers": 1230000,
"phone": "+1 888 926 2289",
"lastUpdated": "2026-09-02T09:41:07Z"
}Three ways to query it
Same schema whichever entry point you use. Pick the one that matches what you already know about the company.
Company Enrichment API
Match a domain or a company name to one verified company with a confidence score.
Company Search API
Build account lists from filters: industry, headcount, location, founding year and more.
Company Social Data API
Turn a LinkedIn company URL into the full structured profile, live or from database.
The company data problems that stall your pipeline
Teams building account-level intelligence run into the same blockers. These are the four that come up before most companies even get to evaluation.
- 01Company records that fracture across rebrands and mergers
- 02Firmographic fields that drift at different speeds
- 03Duplicate accounts that survive every cleanup04Technographic signals too stale to trigger on
Verified before it reaches you
Every company record is resolved to a single stable entity, deduplicated against homonyms and subsidiaries, and refreshed on a demand-scored schedule. Headcount and locations carry a last-updated timestamp.
Read our Data Quality Standard →How teams put this data to work
Four ways teams embed company data today — which fields they use, through which API, and what it changes.
Score and route accounts on live firmographics
A domain comes in from a form or a CRM sync. You resolve it to one company — size, industry, HQ, founding year — and score it against your ICP before a rep ever sees it.
One clean account record per company
Standardise names, fill industry and headcount, attach the logo and LinkedIn page, and merge duplicates on the primary domain. Re-enrich on a schedule so headcount never goes stale.
A company identity layer across your stack
Map every company reference in CRM, billing, product and marketing to a single Reverse Contact ID. Backfill in bulk via CSV, keep it current via API, join on domain everywhere.
Grounded company context for agents
An agent researching an account gets real firmographics — description, positioning, size, HQ — from a verified record instead of scraping or guessing. Exposed through our MCP server.
What makes this company data production-grade
Firmographic APIs are easy to find. The difference shows up when your account data needs to survive rebrands, reconcile subsidiaries, and refresh at the cadence each field actually requires.
Entity resolution across rebrands and subsidiaries
When a company rebrands and moves domains, the API resolves to the surviving entity and links parent and subsidiary records where the relationship is public. Your CRM stops treating one company as three unrelated accounts.
Per-field refresh cadences
Headcount, technographics, and funding refresh on shorter cycles because they change often. Headquarters and founding year sit on longer cadences because they rarely move. Every response includes a last-updated timestamp so you can audit freshness at the field level.
Precision-first matching with confidence scoring
The API returns null when a match falls below the confidence threshold. Every response ships with a confidence score your downstream logic can gate on. Teams running waterfall enrichment plug us in as the primary source or as a strict-precision layer behind a broader provider.
Full firmographic and technographic depth
One call returns identity, industry taxonomy, headcount by department, growth signals across three time windows, technologies detected on the public web, funding history, parent-subsidiary links, and verified social profiles. Your product gets a complete company record from a single endpoint.
Delivery methods that fit the stack you already run
REST API for real-time product features. Webhooks for high-volume enrichment and warehouse backfills. CSV for market mapping and offline analysis. MCP for AI agents that need verified company entities through the Model Context Protocol.
How the company data API works
From a single identifier to a verified company record in four steps.
Step 1: Pass a company identifier
Send a domain, company name, or corporate social URL to the API. The endpoint accepts any of these inputs and resolves on the strongest signal available. Choose real-time retrieval when freshness matters or async processing for high-volume jobs.
Step 2: We resolve and verify the entity
The system matches the input against our data, resolves rebrands and subsidiary relationships, deduplicates candidate records, and scores confidence on the match. If the entity cannot be verified above the threshold, you get null and no credits are charged.
Step 3: Receive a complete company record
The response comes back as a structured JSON object covering identity, firmographics, headcount, technographics, funding, web presence, and metadata. Every field carries a last-updated timestamp so your system knows how fresh each data point is.
Step 4: Route it into your stack
Write the record to your CRM, feed it to a scoring model, load it into a warehouse, or pass it to an AI agent. The schema is stable across every request, so your integration holds whether you enrich ten accounts or ten million.
Built for the compliance conversation you will eventually have
Reverse Contact runs on B2B open-source intelligence with GDPR- and CCPA-aligned practices, documented sourcing, and a working process for data subject rights. Your legal team can review the posture in the Trust Center.
Five questions to ask a company data API before you commit
Most providers work from overlapping raw sources. The difference is what each does with the data afterward and how honestly they describe it.
Match rate by input type
Ask for the rate broken out by input: domain, company name, social URL. A blended number across inputs is a rounded number.
Field-level refresh cadence
Headcount, funding, and technographics need ongoing refresh; slower fields can sit longer. Ask how each field is handled, whether live retrieval is available, and whether every response includes a last-updated timestamp.
Entity resolution
Ask what happens when a company rebrands and moves domains, how mergers get reconciled, and whether parent and subsidiary records link. Vague answers mean a vague pipeline.
Technographic detection quality
Detection accuracy varies enormously. Ask how many categories are tracked, what the detection method is, and how often the stack refreshes. A stale stack sends sales triggers in the wrong direction.
Compliance posture
GDPR and CCPA claims need documentation behind them. Ask for a trust center, a subprocessor list, and specific language on data subject rights.
Trusted by data-driven teams
“Our data team built an internal ops product with Reverse Contact. It improved identity resolution across systems and provided a reliable people & company layer.”
“We use Reverse Contact as a trusted data provider for our product inside our RevOps workflows. It helps our customers unify CRM records and enrich missing context...”
“Reverse Contact provided a reliable identity resolution layer for our product. The API is straightforward, outputs are consistent, and match quality is strong.”
Compliance-by-design. Built to be defensible.
Reverse Contact is designed to support GDPR/CCPA-aligned data practices. We maintain clear sourcing principles, respect data subject rights, and prioritize accuracy over guesswork.
Frequently Asked Questions
Can't find the answers to your questions?
Reach out to us by clicking here.
Structured professional information about individuals in a work context: name, current title, company, work history, education, skills, seniority, industry, and location. Reverse Contact returns all of these through the people data API in a single verified profile.
Identity, professional history, education, skills, languages, location, industry, seniority, social signals, and metadata like last-updated timestamps and confidence scores. Full schema in the Documentation.
We return null instead of a best guess. Every response includes a confidence score so your product decides what to do with borderline matches. You can also raise the precision threshold in your request.
Retrieve profiles live on demand for maximum freshness, or pull from our database for lower latency. Every response includes a last-updated timestamp.
Lookup tools return a name and maybe a title. Our people data API returns a full structured B2B profile per person: identity, professional history, education, skills, location, and more, built to be embedded in products and workflows.
Yes. Compliance is built into how we collect and process data. Full documentation in the Trust Center.
Try it on your own records
500 free credits, 7 days, no card. Run a sample and measure match rate and precision yourself.
How teams put this data to work
Four ways teams embed company data today — which fields they use, through which API, and what it changes.
Score and route accounts on live firmographics
A domain comes in from a form or a CRM sync. You resolve it to one company — size, industry, HQ, founding year — and score it against your ICP before a rep ever sees it.
One clean account record per company
Standardise names, fill industry and headcount, attach the logo and LinkedIn page, and merge duplicates on the primary domain. Re-enrich on a schedule so headcount never goes stale.
A company identity layer across your stack
Map every company reference in CRM, billing, product and marketing to a single Reverse Contact ID. Backfill in bulk via CSV, keep it current via API, join on domain everywhere.
Grounded company context for agents
An agent researching an account gets real firmographics — description, positioning, size, HQ — from a verified record instead of scraping or guessing. Exposed through our MCP server.