Designed for onboarding flows — company autocomplete / pre-fill
The Business Search and Lookup APIs let you search for businesses by name and retrieve full business profiles by registration number.
Registry Data Only These APIs return registry data sourced. Below are list of supported countries.
Austria (AT), Belgium (BE), Cyprus (CY), Czech Republic (CZ), Germany (DE), Denmark (DK), Estonia (EE), Spain (ES), Finland (FI), France (FR), United Kingdom (GB), Greece (GR), Croatia (HR), Hungary (HU), Ireland (IE), Italy (IT), Lithuania (LT), Luxembourg (LU), Latvia (LV), Netherlands (NL), Poland (PL), Portugal (PT), Romania (RO), Sweden (SE), Slovenia (SI), Slovakia (SK), United States (US), Hong Kong (HK), Australia (AU), Singapore (SG)
How it works
These two endpoints work together in a two-step flow:
- Step 1 — Search: User types a company name in your UI. Your backend calls the Business Search endpoint with the
name,country_code, and optionallystate_code. You display the matching results to the user. - Step 2 — Lookup: User selects a company from the results. Your backend calls the Business Lookup endpoint with
business_entity_idandstate_codefrom the selected result. You receive the full profile: legal name, registration status, formation date, registered address, officers, UBOs, and filing events.
Typical integration flow
User starts typing a company name in your onboarding UI.
- Your backend calls Business Search with name, country_code: "US", and optionally state_code (e.g. "DE" for Delaware).
- Display the list of matches — show business_info.name, business_info.entity_type, business_info.state_code, and address if available.
- User selects a company.
- our backend calls Business Lookup with business_entity_id and state_code from the selected item's business_info.
- Use the full profile (business_info, registration_info, related_persons, events) to pre-fill forms or display details.
Authentication
All requests must include your API key in the header:
| Header | Value |
|---|---|
X-API-KEY | Your AiPrise API key |
Content-Type | application/json |
See Authentication for details.
Rate limits
Limits are applied per API key across both Search and Lookup endpoints. Exceeding them returns 429 Too Many Requests. See Rate Limiting for details.
| Window | Limit |
|---|---|
| Per minute | 100 |
| Per hour | 6,000 |
| Per day | 144,000 |
Endpoints at a glance
| Purpose | Method | Path |
|---|---|---|
| Search by name | POST | /api/v1/data/business/search |
| Lookup by registration number | POST | /api/v1/data/business/lookup |
Response format
Both endpoints return data using a consistent structure inspired by AiPrise's standard business objects:
| Field | Description | Available in |
|---|---|---|
business_info | Legal name, entity type, registration number, country, state, addresses. | Search + Lookup |
registration_info | Registry status, formation date, source records with registry URLs. | Lookup only |
Handling addresses
Address data can vary between records. When parsing responses:
- addresses may be null — always check before iterating.
- Either full_address or parsed_address (or both) may be present. Never assume both exist.
- address_type may be null when the registry does not distinguish between registered and mailing addresses.
- source within addresses is typically empty in search results.
Error responses
Both endpoints share the same error codes:
| Status | Meaning |
|---|---|
400 | Bad Request — missing or invalid required fields. |
401 | Unauthorized — missing or invalid X-API-KEY. |
403 | Forbidden — API key lacks required permissions. |
429 | Too Many Requests — rate limit exceeded. |