API Reference/Endpoints

Retrieve a profile

GET/api/linkedin/gateway/users/{identifier}

Looks up a person's public LinkedIn profile by their internal id or their public handle, including how closely they're connected to the account making the call. Pass extra section names to pull deeper details like work history or skills in the same response.

Authentication

Send your personal API key as a bearer token. A missing, malformed or revoked key returns 401. The account behind account_id must belong to your key.

Path parameters

FieldTypeDescription

identifier *stringThe target's internal id (starts with ACo or ADo) or their public handle — the slug in linkedin.com/in/<handle>.

Query parameters

FieldTypeDescription

account_id *stringWhich connected account to view the profile as.

linkedin_sectionsstringExtra profile sections to expand, e.g. experience, education, skills. Use * for everything, or a _preview suffix for a lighter version of a section.

linkedin_api"recruiter" | "sales_navigator"Read the profile through a Recruiter or Sales Navigator seat instead of the standard view, when the account has one.

notifybooleanWhether to leave a "viewed your profile" notification behind. Defaults to false.

Response fields

FieldTypeDescription

resultobject{ object, provider_id, public_identifier, first_name, last_name, headline, network_distance, connections_count }. Requesting linkedin_sections adds matching keys — work_experience, education, skills, and so on — to the same object.

Pulling many full sections back-to-back can get throttled, sometimes coming back empty instead of erroring. Ask only for the sections you need, and space out repeated lookups rather than firing a big batch at once.

Errors

·401 Unauthorized. The key is missing, malformed or has been rotated.·403 Forbidden. The account_id doesn't belong to this key.·404 Not Found. No profile exists for that identifier.