Data APIFor developers

One integration for every B2B data provider.

A REST API with one schema, one key and one bill. Start a search, poll its status and read results as they arrive. You do not choose providers, and you do not maintain an integration with any of them.

Three calls to your first results.

Searches are asynchronous: the API answers at once and you check back for the outcome.

  1. Start a search

    The request returns immediately with the search's id. Send an Idempotency-Key so a retry does not start a second search.

    POST /v1/companies/search
    Authorization: Bearer $AVINA_API_KEY
    Idempotency-Key: 7f3c2a9e
    {
      "query": "Privately held dental practices in Texas hiring SDRs",
      "limit": 5,
      "max_credits": 5
    }
    
    202 Accepted
    { "id": "32ba40da", "status": "queued" }
    
  2. Poll its status

    Poll with backoff until the status is completed, failed or cancelled. stop_reason says why the search stopped.

    GET /v1/companies/search/32ba40da/status
    
    200 OK
    {
      "status": "completed",
      "stop_reason": "target_reached",
      "credits_charged": 2.31
    }
    
  3. Page through the results

    Read results while the search runs or after it ends. Pass the previous next_cursor as after until has_more is false.

    GET /v1/companies/search/32ba40da/results?after=cursor
    
    200 OK
    {
      "data": [ ... ],
      "next_cursor": "...",
      "has_more": false
    }
    

Why developers build on it.

No provider integrations
Company databases, job listings, technology data, AI search and contact providers sit behind one request. Results arrive in one schema, with one record per company.
Safe to retry, easy to stop
An Idempotency-Key makes a start request safe to retry. A client timeout does not stop a search, and a cancel call does.
Docs your coding agent can read
Every docs page is available as Markdown, with an llms.txt index, an OpenAPI 3.1 spec and an integration brief to paste into your agent.

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.

  1. 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.

  2. 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.

  3. Verify

    Each candidate is checked against every requirement. It passes only when every requirement is matched with evidence.

  4. 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.

Who else builds on the Data API.

Common questions

How do I get an API key?

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.

Are searches synchronous?

No. Starting a search returns 202 with the search's id straight away. You poll its status and read results page by page, including while it is still running.

What does it cost to develop against?

Parse, reading status and reading results are free, and requests rejected with a 4xx error are not charged. Starting a search spends credits, so use a small limit and a small max_credits while you build.

How do errors work?

Every error has the same shape, with a code, a message and a request id. Branch on the code. Retry a 429 after the Retry-After interval and retry 5xx errors. Do not retry other 4xx errors.

The last B2B data integration you’ll write.

Request beta access, then follow the quickstart to your first results.

The Data API is in beta. Access is by request.