Baselayer International

Two of Baselayer's core US products - Business Search and Web Presence - have international counterparts for verifying businesses outside the United States.

• International Business Search returns corporate registration data (name, registration number, status, legal form, and more) for businesses in 75+ countries and territories, sourced from foreign corporate registries.
• Web Presence works internationally out of the box * the same endpoint and response structure you already use for US businesses, with global coverage.

This is the Basics of Baselayer International. For the Business Verification product, see also the API Quickstart and Best Practices.

At a Glance: US vs. International

International Business Search

How It Works

International Business Search is available using a separate set of endpoints from the US Business Search. Data returned maintains a consistent structure across jurisdictions, though information depth varies by country.

Two Ways to Search

POST /international/searches accepts two ways to identify a business. Both require iso2_country_code.

• Name + address: provide name and address. The standard approach, and all you need for the vast majority of searches.
• Registration (filing) number: provide filing_number. A good optional input to offer: in many countries, owners and finance staff know their registration number by heart. When provided, the registry is searched by that number first; a name, if also included, is used as a fallback if no company matches the number.

Tip: Label the registration-number field with the local term so users recognize it. In Spain, for example, it's the CIF. If you want to smooth matching in a specific market, you can also look candidates up first with GET /international/registrations (see below). Both are optional, a plain name + address search works well on its own.

Supported Countries

International Business Search is available for the following 76 jurisdictions.
★ = Enhanced Profile available (see Enhanced Profiles); all others return the core profile.

37 of the 76 jurisdictions offer Enhanced Profiles (★).

Note: Country availability reflects current registry access and may change over time. The iso2_country_code must be one of the supported jurisdictions above, submitting an unsupported code returns a validation error. Contact your account manager for the latest list.

API Endpoints

POST /international/searches
GET  /international_searches/{id}
GET  /international_searches
GET  /international/registrations

For the complete API reference, see Post International Search and Search International Registrations.

Making a Request

A request always requires iso2_country_code, plus either name + address or filing_number.

POST /international/searches

{
    "name": "Acme Ltd",
    "address": "1 Parliament St, London SW1A 2JR, United Kingdom",
    "iso2_country_code": "GB"
}

Optional fields include:

• filing_number — the company registration number (see Two Ways to Search above)
• officer_names — known officers or directors
• website — business website URL
• phone_number — business phone number
• email — business or contact email
• alternative_names — trading names or DBAs
• reference_id — your internal ID for tracking this request
• options — separately-billed add-ons (see Enhanced Profiles below)

Enhanced Profiles (optional)

By default a search returns the core registration profile: name, file number, status, addresses and officers. In supported jurisdictions (★ above), you can request an Enhanced Profile with the Order.Enhanced option, which adds directors, ultimate beneficial owners (UBOs), shareholders, and share capital where available.

POST /international/searches
{ "filing_number": "01234567", "iso2_country_code": "GB", "options": ["Order.Enhanced"] }

Enhanced Profiles are billed separately, per country, and coverage varies by jurisdiction. Contact your account manager for complete details.

International Registrations Search

GET /international/registrations returns a list of matching registrations without running a full search. Its main use is to disambiguate before a precise search: look up candidates, let your user pick the right one, then search with that result's filing_number.

GET /international/registrations?iso2_country_code=GB&name=Acme%20Ltd

Query parameters: iso2_country_code, name, and/or filing_number. This is an optional add-on, most useful where several businesses share a similar name.

Understanding the Response

When a search completes, the response includes a business object. The following fields are present across all countries:

• name: the official registered name
• file_number: the registration/filing number in the local registry
• status: normalized to active, inactive, or unknown
• country: the ISO2 country code of the registration

The response also reports how well your inputs matched the company found, the same match signals as the US Business Search:

• business_name_match: EXACT, SIMILAR, or NO_MATCH (identical to the US)
• business_address_match: EXACT, CITY, REGION, COUNTRY, or NO_MATCH (international granularity)
• filing_number_match: a boolean specific to international search: true if the filing_number located the company, false if the search fell back to the name, null if no filing number was provided

Important: Data depth varies significantly by country. Most countries return the core fields above; some return more.

Scores & Ratings

International Business Search returns the same KYB and Risk ratings as the US product, calculated using the same methodology and value scale, so you can apply the same thresholds and decisioning logic you already use for US searches. See Scores & Ratings.

Webhooks

International Business Search emits three webhook events:

• InternationalBusinessSearch.submitted: accepted and processing
• InternationalBusinessSearch.completed: results available
• InternationalBusinessSearch.failed: no associated business found

These follow the same structure as US Business Search webhooks. See the Webhooks Guide.

Key Differences from US Business Search

• Separate API route: international searches use /international/searches, not /searches. The two are not interchangeable.
• No TIN verification: IRS TIN matching is a US-only capability.
• Online-presence add-ons: for website analysis, industry prediction, and other online-presence signals internationally, use the Web Presence endpoint (below).
• Country-specific pricing: negotiated separately from your US contract.
• API-only access: not available through the Console (yet).

Web Presence (International)

How It Works

Baselayer's Web Presence endpoint works internationally using the same API route and response format as US requests. When you include a non-US iso2_country_code, Baselayer automatically routes the request through its international processing pipeline; the response structure is identical.

Web Presence is available via both the API and the Baselayer Console.

Supported Countries

Web Presence offers global coverage: any country with a valid ISO 3166-1 alpha-2 code is supported. This is much broader than International Business Search because Web Presence relies on Baselayer's AI-powered web intelligence rather than corporate registry access.

API Endpoint

POST /web_presence_requests
GET  /web_presence_requests/{id}
GET  /web_presence_requests

This is the same endpoint used for US Web Presence. See Post Web Presence Request.

Making a Request

Include the iso2_country_code field; the minimum required fields are name and address.

POST /web_presence_requests

{
    "name": "Siemens AG",
    "address": "Werner-von-Siemens-Straße 1, 80333 München, Germany",
    "iso2_country_code": "DE"
}

Optional fields that improve results include website, officer_names, phone_number, email, alternative_names, reference_id, and options. See Online Presence: Basics.

Understanding the Response

The response mirrors the US response. The request_type field is set to INTERNATIONAL (instead of UNITED_STATES), and you receive the same key data points. See the Web Presence & Orderables Guide.

Webhooks

Web Presence uses the same webhook events for both US and international requests:

• WebPresenceRequest.submitted: accepted and processing
• WebPresenceRequest.completed: results available
• WebPresenceRequest.failed: could not be completed

Quick Reference

International Business Search

Web Presence (International)

Where to Go Next

• International Business Search: API Quickstart: Step-by-step, from request to response.
• International Business Search: Best Practices: Search inputs, Enhanced Profiles, match indicators, and what varies by country.
• Scores & Ratings: How KYB and Risk ratings are calculated.
• Webhooks: Configuring event delivery.