Solutions Company Search API
Company Search API: targeted B2B account lists
Turn structured firmographic criteria into targeted B2B account lists your product, workflow, or analytics team can act on at scale.
POST /v2/search/companies
Live · production API
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
200 OK36 fieldssample
{
"success": true,
"data": {
"data": [
{
"id": "com_01jc2x8q5n3v7b1m9k4t6r0e2a",
"name": "Stripe",
"publicId": "stripe",
"linkedinId": "18919",
"linkedinUrl": "https://www.linkedin.com/company/stripe",
"employeesCount": 8000,
"industry": "Financial Services",
"location": {
"city": "San Francisco",
"country": "US"
}
},
{
"id": "com_01jd9h3w6p0s4v8z2c5f7k1m3q",
"name": "Notion",
"publicId": "notionhq",
"linkedinId": "13343370",
"linkedinUrl": "https://www.linkedin.com/company/notionhq",
"employeesCount": 850,
"industry": "Software Development",
"location": {
"city": "San Francisco",
"country": "US"
}
},
{
"id": "com_01je5n8r1t4w7y0b3d6g9j2m5p",
"name": "Figma",
"publicId": "figma",
"linkedinId": "10054583",
"linkedinUrl": "https://www.linkedin.com/company/figma",
"employeesCount": 1500,
"industry": "Software Development",
"location": {
"city": "San Francisco",
"country": "US"
}
}
],
"metadata": {
"currentPage": 1,
"pageNumber": 2,
"perPage": 100,
"total": 184
}
},
"error": null
}curl -X POST https://api.reversecontact.com/v2/search/companies \
-H "Authorization: Bearer <API_KEY>" \
-H "Content-Type: application/json" \
-d '{}'import requests
res = requests.post(
"https://api.reversecontact.com/v2/search/companies",
headers={"Authorization": "Bearer <API_KEY>"},
json={},
)
print(res.json())const url = "https://api.reversecontact.com/v2/search/companies";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: "Bearer <API_KEY>",
"Content-Type": "application/json",
},
body: JSON.stringify({}),
});
console.log(await res.json());Benefits
Search results built for production workflows
Predictable schemas, clear freshness signals, and consistent output keep account list building and segmentation repeatable across every run.
Powerful filters
Search by industry, headcount, location, and revenue to build account lists that match your ICP without manual research.
Predictable output
Every response returns the same normalized schema, so you can store, dedupe, and join without writing custom parsing logic.
Built for scale
Cursor-based pagination and a stable schema keep integrations reliable under high volume, from hundreds to hundreds of thousands.
Use cases
How teams put this data to work
Account list building
Build account lists by industry, size, and geography using structured filters. Consistent targeting without manual research or spreadsheet cleanup.
TAM & market mapping
Size your addressable market and map segments by industry, headcount, and geography for repeatable GTM planning.
ABM target lists
Combine multiple firmographic constraints in one request to build ABM lists and route them to the right owners.
Data warehouse sourcing
Load structured company records into your warehouse with stable identifiers, so downstream joins and analytics stay clean.
Territory planning
Generate territory-ready account lists by region, segment, and size threshold, and cut the data-cleaning step out of GTM planning.
AI agent discovery
Let AI agents retrieve company entities on demand, grounded by freshness timestamps and confidence signals per record.
ICP refinement and testing
Test and iterate your ICP by running structured queries, then pull matched account lists as the definition sharpens.
Adjacent market discovery
Expand from your current book into adjacent markets by finding companies with firmographic profiles matching your best accounts.
Process
How the Company Search API works
A synchronous request-response flow you can call in real time, with page-based pagination for higher-volume runs.
- 01
Set your filters
Choose your filters: industry, headcount, location, revenue. Set pagination and precision defaults for the query you want to run.
- 02
Call the Search API
Send your query. Page through results with page-based pagination until you have the full match set for the filters you sent.
- 03
Use the results
Use returned company IDs to fetch full profiles, build account lists, or trigger enrichment and routing workflows downstream.
Comparison
What to check when comparing company search APIs
Most search endpoints work from overlapping raw sources. Filter depth, result precision, and freshness signals are where the difference actually shows up in production.
Filter granularity
Look for depth beyond industry, headcount, and country. Check how narrow you can scope location, and whether headcount bands map to your real GTM segments rather than round numbers.
Result precision
Ask what the false-positive rate is at the top of the result set, and whether you can set a confidence threshold on the endpoint.
Freshness signals
Every response should include a companyUpdateDate timestamp per record, not just at the API level.
Pagination and schema stability
Ask whether pagination is cursor-based, which holds up on long-running exports, or offset-based, which drifts. Confirm the response schema stays stable across API versions so integrations do not break on upgrade.
Compliance posture
GDPR and CCPA claims should come with documentation: a trust center, a subprocessor list, and clear language on data subject rights. Ask for links, not promises.
Testimonials
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.”
Ethan CarterData Team, Gitpod“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...”
David BrombergCEO, Lantern“Reverse Contact provided a reliable identity resolution layer for our product. The API is straightforward, outputs are consistent, and match quality is strong.”
Lucas PerretHead of Product, lemlistCompliance
Compliance-by-design. Built to be defensible.
Reverse Contact runs on B2B open-source intelligence with GDPR and CCPA-aligned data practices. We document sourcing, respect data subject rights, and return null instead of guessing when confidence is low.
- GDPR
- CCPA
FAQ
Frequently Asked Questions
Can't find the answer to your question? Reach out to us via the contact page.
Can I try the Company Search API before committing?
Yes. Start with pay-as-you-go credits and no subscription, or ask for an evaluation plan on a demo call. Either path lets you test data quality and integration fit against your real inputs before signing anything.
<strong>What company fields does the Company Search API return?</strong>
The search response includes company name, LinkedIn identifiers, employee count, industry, and location (city and country) per match. The schema is stable across every response, so you can store and join without custom parsing per request. For the full field set including firmographics and technographics, use the returned IDs with the Company Enrichment API or see the full company data schema.
<strong>How do you handle false positives?</strong>
The API returns null when confidence falls below the threshold, and every match ships with a confidence score you can gate on. Teams running waterfall enrichment plug the endpoint in as a strict-precision source alongside a broader provider.
<strong>How fresh is the company data?</strong>
You can resolve records live on demand for maximum freshness, or query the database for lower latency. Every response includes a companyUpdateDate timestamp so your system can decide when to re-fetch a record.
<strong>What is the difference between Company Search and Company Enrichment?</strong>
Company Search takes firmographic filters and returns a list of matching companies you did not have before. Company Enrichment takes a company you already have, such as a domain or LinkedIn URL, and fills the record. Search is for discovery. Enrichment is for completing what you already hold.
<strong>Can I combine Company Search with People Search in one workflow?</strong>
Yes. A common pattern: use Company Search to build an account list against firmographic filters, then feed the returned company IDs into People Search to discover contacts inside those accounts. The two endpoints share identifiers, so the handoff stays clean.
Build B2B account lists your product can rely on.
Access verified company data through one API. Build the account lists your ICP calls for, with output clean enough to trust every step downstream.
- Profiles
- 1B+
- Refreshes / month
- 200M
- Response time (P95)
- 500ms