ChatGPT ↗
Claude ↗This page documents the canonical HTTP contract for this endpoint.
This read endpoint requires linkedin:read for developer API keys; authenticated user sessions are also accepted. It resolves against the caller’s current/default LinkedIn connection and has no sender-account selector. For a matching organization lead, it can force a provider relationship refresh and persist the resulting relationship snapshot; otherwise it looks up the public profile through the provider.
The response model exposes resolved, slug, connection_degree, relationship_label, is_relation, connection_state, source, stale, checked_at, and optional message. Degree values can be null when unresolved. is_relation is true only when the reported degree is first-degree; false or null do not imply an error.
Query parameters
linkedin_urlrequiredstring
LinkedIn profile URL or slug to look up. This is a query parameter and must be URL-encoded when needed.
| Name | Type | Description |
|---|---|---|
| linkedin_urlrequired | string | LinkedIn profile URL or slug to look up. This is a query parameter and must be URL-encoded when needed. |
Errors
| Status | Meaning |
|---|---|
| 401 | Invalid API key or missing auth. |
| 403 | Developer API key lacks linkedin:read scope. |
| 400 | Organization/user context is missing, LinkedIn is not connected, or profile URL is invalid. |
| 424 | The connected account requires reconnect for this operation. |
| 502 | Fallback when the provider error has no HTTP status; a provider HTTP status may otherwise be returned. |
| 422 | Required query parameter linkedin_url is missing. |
| 503 | Unipile LinkedIn integration is not configured. |