Skip to main content
Every search returns a single JSON object. All top-level fields are always present — disabled features return null rather than being omitted.

Top-level shape


meta

Metadata about the search itself. Your original query is nested under submitted.
completed-with-errors means at least one data source succeeded. Check the errors object to see which sources failed.

businesses

An array of business registry matches, sorted by match confidence.

regulatory

Flat arrays of regulatory registry matches. Empty arrays when no matches are found.
Each item includes legalName ({name, matchScore}), registrationNumber, status, addresses, and a sourceUrl linking to the official registry record.

sanctions

Always present in the response. null when sanctionsScreening is false. When enabled, an object with query, totalMatches, and matches. See Sanctions screening for full documentation.
This describes the sanctions field within a search response. For the standalone POST /sanctions endpoint, which has its own meta, screening, and sourceCounts structure, see Standalone screening.

website

Always present in the response. null when websiteAnalysis is false and no website URL was provided.
See Website analysis for full field documentation.

errors

Always present in the response. null when all sources succeeded. The search can still succeed (completed-with-errors) even if some sources fail.
Keys correspond to data sources: businessRegistry, regulatoryRegistry, sanctionsScreening, websiteAnalysis. Only failed sources appear — a key’s absence means that source succeeded. See Error handling for the full list of error codes.