The Search API allows you to find and screen companies at scale by running a query, a tree of filters, against Veridion's company universe. A single module parameter sets what question that query answers: find a specific company, verify one you already hold, segment a market, or discover suppliers.

When to use it

Reach for this endpoint once you know which module fits your job and which filters express your criteria:

• Find a company you can describe but not identify, with company_lookup.
• Verify a company you already hold against a set of conditions, with company_verification.
• Segment a market into the companies that meet your criteria, with segmentation.
• Discover suppliers of a product or service, with supplier_discovery.

Request body

The body is a module plus a query (the filter tree):

{
    "module": "company_verification",
    "query": {...}
}

Where module is one of company_lookup, company_verification, segmentation, or supplier_discovery.

For how to compose query, see How to build a search query; for each module's required anchor and allowed filters, see Choosing a module.

Results pagination

Results are paginated using the same cursor based mechanism as other Veridion APIs. See the Pagination section for the parameters and tokens.

Successful responses

A successful call returns 200 OK with a JSON envelope. Each company in result carries its evidence first (if evidence is required), then its company fields.

{
  "search_module": "supplier_discovery",
  "result_count": 1240,
  "result": [
    { "evidence": { }, "veridion_id": "…", "company_name": "…" }
  ],
  "has_more": true,
  "next_cursor": "eyJ0IjoicyIs…"
}

For the company fields inside each result, see Response fields and types; for more details on the evidence object, see Explainability (evidence).

Error responses

• 400 Bad Request, where the body breaks a module's input contract, or the query is malformed. When a filter isn't allowed in the module you called, the message names the module you should use instead, so a caller can correct and retry. See Choosing a module.
• other standard HTTP error responses, detailed in the Response codes section.

Any error response follows a specific structure. Please see the Error response format section for more details.