Social platforms

List LinkedIn profiles similar to a user · LinkedIn API

GET/linkedin/users/{username}/similar
$$min $0.02

Returns LinkedIn profiles that LinkedIn shows as similar to a user ("People also viewed").

Using ChatGPT, Claude Code or another client? See the setup steps

Request
curl https://api.unifapi.com/linkedin/users/{username}/similar \
  -H "Authorization: Bearer $UNIFAPI_KEY"

Parameters

usernamepathrequired
LinkedIn vanity username (as in linkedin.com/in/{username}) or entity id (`ACoAA…`).
The parameter for this LinkedIn operation. Use the URL-visible slug or id described in the docs.
Overview

This operation is part of the LinkedIn API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs LinkedIn public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.

Common agent workflows

  • Resolve a public LinkedIn identity into structured profile metadata for enrichment agents.
  • Refresh creator, company, or account snapshots without managing source-specific response shapes.
  • Give an AI agent a stable LinkedIn data source without building a per-platform integration.
  • Normalize LinkedIn responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
  • The operation has a 18 credits ($0.02) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
  • If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.

Response status codes

200400401402404429500502503

Billing

This operation charges 1 credit per billable record, with a 18 credits ($0.02) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.

Errors and retries

Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.

Response fields

Fields on each record in data

A successful List LinkedIn profiles similar to a user call returns data as an array; each record carries these fields (12 of 48 shown — the docs list the full schema).

data_idstring | null
Stable Data API person identifier (`prsn_…`) when observed.
live_numeric_idstring | null
Live numeric person identifier, serialized as a string when observed.
entity_idstring | null
LinkedIn person entity ID when observed.
usernamestring | null
Public LinkedIn handle when observed; falls back to the `/in/` segment of `profile_url`.
profile_urlstring | null
Canonical LinkedIn profile URL when observed; falls back to the URL built from `handle`.
first_namestring | null
First name when observed.
last_namestring | null
Last name when observed.
full_namestring | null
Full name when observed; falls back to `first_name` and `last_name` joined with a space.
headlinestring | null
Professional headline when observed.
summarystring | null
Profile summary when observed.
profile_picture_urlstring | null
Primary profile picture URL when observed.
profile_picturesobject[]
Profile image variants when observed.