Get a LinkedIn user profile by URL slug · LinkedIn API
Returns the canonical LinkedIn profile for the given URL slug (`public_identifier`). Returns 404 not_found if no such user exists.
curl https://api.unifapi.com/linkedin/users/{username} \
-H "Authorization: Bearer $UNIFAPI_KEY"Parameters
- usernamepathrequired
- LinkedIn URL slug, e.g. `williamhgates`
- The parameter for this LinkedIn operation. Use the URL-visible slug or id described in the docs.
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 but should still keep one API key, one account balance, and one predictable JSON contract across social, live public-data sources.
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.
Unified envelope, platform-native fields
- Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
- The `billing.records_charged` field reports the charged billable-record quantity for the successful response.
- A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.
Response status codes
Billing
This operation charges 1 credit per billable record, with a 1 credit ($0.001) 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.
Fields in the data object
A successful Get a LinkedIn user profile by URL slug call returns one data object with these fields (12 of 20 shown — the docs list the full schema).
- idstring
- LinkedIn URL slug (public_identifier). Use this as the path parameter for every /linkedin/users/{id}/... endpoint.
- urnstring
- LinkedIn internal URN (e.g. `ACoAA...`). Stable across username changes; required by certain LinkedIn-internal flows.
- usernamestring
- Same value as `id`; included for cross-platform field parity.
- display_namestring
- first_namestring
- last_namestring
- headlinestring
- avatar_urlstring
- cover_image_urlstring
- locationobject
- is_premiumboolean
- is_open_to_workboolean
Agents & Skills built on LinkedIn
You rarely call Get a LinkedIn user profile by URL slug by hand. These prebuilt agents and skills already read LinkedIn data inside Claude or Codex — start from one of them, or call this endpoint yourself.
Try it free in the browser
More LinkedIn operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
Search LinkedIn jobs by keyword and filters
Search LinkedIn job postings by keyword and filters as a cursor-paginated list. This operation is capacity-limited; the gateway makes up to 3 total attempts for transient failures.
List posts authored by a LinkedIn user
Return posts authored by a LinkedIn user from the profile URL slug as a cursor-paginated list. This operation is capacity-limited; the gateway makes up to 3 total attempts for transient failures.
Get a LinkedIn company profile by URL slug
Return a canonicalized LinkedIn company profile by its URL slug (`universal_name`, e.g. `microsoft`), including description, industry, size, headquarters, and the numeric `company_id` that related endpoints use. Useful as the entry point for any company-level research.
List posts published by a LinkedIn company page
Return posts published from a LinkedIn company page by URL slug as a cursor-paginated list. This operation is capacity-limited; the gateway makes up to 3 total attempts for transient failures.
Get a LinkedIn job posting by ID
Return a LinkedIn job posting by ID, including title, company, location, description, and optional skills or hiring-team data. This operation is capacity-limited; the gateway makes up to 3 total attempts for transient failures.
Get a LinkedIn post by ID
Return a single LinkedIn post by its numeric ID, including author, text, media, and engagement counts. Useful for hydrating a known post or checking its current reach.