Data APIFor data teams
One schema for company and people data, whoever supplied it.
Results are normalized into one schema and merged into one record per company, so a company looks the same whichever provider found it. Every record carries the evidence for why it matched.
Built for a pipeline.
Exact conditions in, one record per company out, and the cost of each run on the search itself.
Filter on exact fields
A technology, a country or a size written as a filter is checked against data records, which costs less than a free-text requirement.
POST /v1/companies/search { "filters": { "all": [ { "field": "company.technologies", "operator": "in", "value": ["Salesforce"] }, { "field": "company.headquarters.country", "operator": "in", "value": ["US", "CA"] }, { "field": "company.employee_count", "operator": "gte", "value": 100 } ] }, "limit": 50, "max_credits": 40 }Get one record per company
Each result lists the requirements it was checked against, with a verdict, a summary and the sources. Example values are illustrative.
{ "name": "Lakeview Dental Group", "domain": "lakeviewdental.example", "matched_criteria": [{ "criterion": "open_jobs", "verdict": "matched", "evidence": { "summary": "1 open job matches.", "sources": ["https://lakeviewdental.example/careers/sdr"] } }] }Know what each run cost
The search's own credits_charged field is the source of truth. It updates while the search runs and is final once it ends.
GET /v1/companies/search/32ba40da/status 200 OK { "status": "completed", "stop_reason": "target_reached", "credits_charged": 2.31 }
Why data teams use it.
- Deduplicated before it reaches you
- Candidates are merged into one record per company website before they are checked and counted. Your limit counts distinct companies, not provider rows.
- No guesses in the data
- A requirement is matched, not matched or unknown. Missing data is not a no, an unknown is not a yes, and an imprecise figure is not rounded in your favor.
- No vendor contracts
- One account covers every provider. You do not sign a contract with any data provider.
How a request is answered.
Every search goes through the same four stages. You do not choose providers, and you can see what each stage did.
Interpret
The request is turned into exact requirements: filters on known fields, and free-text criteria for anything no field covers. Nothing you asked for is dropped.
Route
Avina picks the sources from what the request contains: data providers for structured conditions, AI search of the public web for requirements that need research.
Verify
Each candidate is checked against every requirement. It passes only when every requirement is matched with evidence.
Return
Passing records are merged into one per company or person and added to the results, which you can read while the search is still running.
The APIs behind it.
One key covers all of them. Each links to its page in the docs. See all seven.
- CompaniesAvailableFind companies by anything you can describe: filters, requirements no database covers, and events like a new hire or a funding round.
POST /v1/companies/search - PeopleAvailableFind people by job title, seniority and employer, with verified work emails on request.
POST /v1/people/search - ParseAvailableTurn plain language into structured filters you can show, edit and reuse. Free.
POST /v1/companies/search/parse - EnrichAvailableFill in missing fields for companies and people you already have.
POST /v1/enrich
Who else builds on the Data API.
Common questions
Which provider did a record come from?
Provider names are not part of the response. Results are normalized into one schema, and each requirement on a result cites the sources of its evidence.
How are duplicates handled?
The same company can come back from several providers under slightly different names. Avina merges candidates into one record per company website domain, so a company appears once in a search's results.
How do I keep a run within budget?
Set max_credits on the search. It stops new spending when it reaches the limit and keeps the results found so far. Reading status and results is free.
How do I get access?
The Data API is in beta. Request access with the form in the docs. Once you are in, a workspace admin creates an API key in the Avina dashboard and adds credits, and the quickstart takes you to your first results.
One source for company and people records.
Request beta access and run your first search in minutes.
The Data API is in beta. Access is by request.