ChatGPT ↗
Claude ↗This page documents the canonical HTTP contract. Switch to the CLI example when you want the operator workflow.
This read endpoint uses the caller’s resolved LinkedIn connection and requires linkedin:read for developer API keys; authenticated user sessions are also accepted. No sender-account selector is accepted. The response is passed through from the provider; item fields and pagination are provider-defined.
Path parameters
post_idrequiredstring
Provider post ID. The handler documents LinkedIn `social_id` format such as `urn:li:activity:7177842619385757696`; URL-encode reserved characters in the path.
| Name | Type | Description |
|---|---|---|
| post_idrequired | string | Provider post ID. The handler documents LinkedIn `social_id` format such as `urn:li:activity:7177842619385757696`; URL-encode reserved characters in the path. |
Query parameters
cursor· optionalstring
Pagination cursor from a previous response.
limit· optionalinteger
Results per page, 1–250. Default: 100.
| Name | Type | Description |
|---|---|---|
| cursor | string | Pagination cursor from a previous response. |
| limit | integer | Results per page, 1–250. Default: 100. |
Errors
| Status | Meaning |
|---|---|
| 401 | Invalid API key or missing auth. |
| 403 | Developer API key lacks linkedin:read scope. |
| 400 | Organization/user context is missing or LinkedIn is not connected. |
| 424 | The connected account requires reconnect for this operation. |
| 429 | Account policy does not currently allow the request. |
| 502 | Fallback when the provider error has no HTTP status; a provider HTTP status may otherwise be returned. |
| 422 | Query limit is outside 1–250. |
| 503 | Unipile LinkedIn integration is not configured. |