Get LinkedIn post details

Returns detailed information about a specific LinkedIn post including the post text, like count, comment count, share count, author info, media attachments, and publish timestamp.

Which post URL to send. A LinkedIn post can be addressed by three different ids, and this endpoint resolves the ACTIVITY one: https://www.linkedin.com/feed/update/urn:li:activity:<id>, or the share-button form https://www.linkedin.com/posts/<slug>-activity-<id>-<code>. A urn:li:share: or urn:li:ugcPost: URL is a different id for the same post and cannot be resolved here, so it is rejected with a 400 before any credits are charged. The reliable way to get a URL that works is to read post.url off any endpoint that lists posts (/v1/linkedin/profile/posts, /v1/linkedin/company/posts, /v1/linkedin/search/posts and the rest): that field is always the activity form. Do not rebuild the URL from post.id, which on some lanes is the share or ugcPost id rather than the activity id.

get/linkedin/post

Request

Base URL: https://www.socialcrawl.dev/v1
URL: https://www.socialcrawl.dev/v1/linkedin/post
Auth: API key in header x-api-key

Query parameters

urlstring required

Full URL of the LinkedIn post. It has to carry the post's ACTIVITY id, either https://www.linkedin.com/feed/update/urn:li:activity:<id> or https://www.linkedin.com/posts/<slug>-activity-<id>-<code>. A urn:li:share: or urn:li:ugcPost: URL names a different id for the same post and is rejected with a 400 before any credits are charged, because it cannot be resolved to the post. Every endpoint that lists posts publishes the activity form as post.url, so copy that field rather than rebuilding the URL from post.id, which is not always the activity id.

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "linkedin",
  "endpoint": "/v1/linkedin/post",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.