Introduction
The People Lookalike endpoint returns the people who look like one seed profile. You name the seed by its Social profile URL or by its Reverse Contact person id (prs_...), and the search is built from what the seed does today: its current function and sub-function, with the time it has spent in them when it is known, its current seniority and its location (country and city). The seed itself is never part of the results.
Every result is a complete profile, the same shape People search returns, with the same cursor pagination and the same price: 1 credit per profile delivered. Results are drawn from our cache-based search index. This endpoint never triggers a live fetch.
Use it when you know one good profile and want more people like it. To choose the criteria yourself, use People search.
Authorization
apikey
string
required
Authorization: Bearer YOUR_API_KEY header.Request body
Provide exactly one seed: url or id. Sending both returns HTTP 422, because a lookalike is built from a single profile.
url
string
conditional
https://social.com/in/janedoe). Required unless id is given.id
string
conditional
prs_01jbd5vewyenebxgaz869ffe5t), as returned in the id field of any person response. Required unless url is given.cursor
string
metadata.nextCursor; request the next pageperPage
number
25)No filters: the search criteria come from the seed, so the request takes no search filter. Any other field, such as
locationorcurrentSeniority, returns HTTP422witherror.codeLOOKALIKE_FILTERS_NOT_SUPPORTEDand the offending fields inerror.details.fields, and costs 0 credits. A filter is refused rather than ignored, because an ignored filter would return results you did not ask for.
Seed checks: the seed must already be in our search index. A profile that is not indexed yet returns HTTP
404and costs 0 credits: no lookalike can be built from it, so try another seed. Anidthat matches no profile returns HTTP422witherror.codeVALIDATION_ERROR, and a seed under an active data subject request (GDPR/CCPA) returns HTTP451witherror.codeDATA_SUBJECT_BLOCKED. Neither costs credits.
Pagination and credits
People lookalike uses cursor pagination, like People search. Each response returns up to perPage profiles (1 to 100, default 25) and a metadata.nextCursor value. To get the following page, send the same seed again with that value as cursor; nextCursor is null on the last page. The cursor is opaque: send it back unchanged, without parsing or altering it. There is no page parameter.
perPage above 100 returns HTTP 422 with error.code PAGINATION_LIMIT_EXCEEDED, and a perPage that is not a whole number returns HTTP 422 with error.code INVALID_PAGINATION.
People lookalike costs 1 credit per profile delivered. Compliance-blocked profiles are removed before the response and are not billed. A page that returns 25 profiles costs 25 credits, and a page that returns no profile costs 0 credits. Lower perPage to control how many credits a single request can spend.
Response structure
Note: This endpoint uses a nested envelope. The top-level V2
datafield wraps an inner search payload that contains the actual results array (data.data) and the pagination info (data.metadata). See the example response for the exact shape.
success
boolean
true if the request was processed successfullyerror
null
null on success