Skip to main content
POST
Lookalike

Credits and plans

PAYG is Pay-as-you-go. AYCE is All-you-can-eat.

When to use Lookalike

Start from a company you already know and inspect nearby companies. This endpoint returns company records, rather than the people who work there. For a contact or company audience with other criteria, use a lookalike filter on Count, View, Preview, or Export.

Example

Set REVENUEBASE_API_KEY to your API key.
Response captured from the local test API on October 13, 2026 using an AYCE account. Results can change as the dataset or account changes.

Read the response

rbidOrg identifies the resolved seed. matches is an ordered list of other companies, with rbidOrg, similarity, a match classification, and requested company fields. Higher similarity is closer to the seed. The seed itself is excluded. A match classification can be null when it falls outside the named tiers.

Options and limits

The standalone request accepts these options. The match and maxDistance controls belong to the lookalike filter node, which you use when defining an audience.

Errors and next steps

An unresolved seed or one without usable similarity data can fail with a 404 or 422 response. Choose another seed or retrieve its company record first. Company Enrich retrieves known company identifiers. A lookalike filter lets you count an audience before choosing an inline response or file.

Authorizations

X-Key
string
header
required

Body

application/json
domain
string | null

Seed company domain. Supply domain or rbidOrg.

rbidOrg
string | null

Seed company identifier. Takes precedence when both identifiers are supplied.

limit
integer | null

Number of nearest companies; defaults to 25 and is clamped to 1 through 200.

columns
string[] | null

Company fields to return; ["*"] requests all company catalog fields.

Response

Successful Response

The response is of type Response Lookalike V1 Company Lookalike Post · object.