Walk a LinkedIn member's COMPLETE post history, 100 posts a page, with exact publish times and share counts the other lanes cannot return. Metered: 5 credits per post returned, so try the cheaper /v1/linkedin/profile/posts first
Returns a LinkedIn member's posts read from their own feed rather than from a public search index, and it is the only route that reaches a member's complete history. Measured on one prolific member 07/09/2026: this endpoint walked about 1,800 posts back to June 2017 and then stopped because there was nothing older, while /v1/linkedin/profile/posts caps at 100 and walking /v1/linkedin/search/posts with from_member exhausts at about 395. How far back it reaches is a property of the member, not of this endpoint: when a page comes back with no next_cursor, you have everything. Each post carries the text, media, the exact publish timestamp and the full engagement breakdown including share counts. It is not the cheapest lane. /v1/linkedin/profile/posts returns up to 50 posts for a flat 5 credits, or up to 100 at 2 credits a post, and is the whole history for most members, so start there and come here when it is not enough, or when you need what it cannot give you: an exact publish timestamp on every row instead of an approximation that shifts between calls, the share count, and a guarantee that every row was written by the member rather than reshared by them. To walk the archive, pass limit=100 and follow next_cursor until it stops coming back. A limit below 100 returns that many of the newest posts and no cursor, because a partial page cannot be continued without silently skipping the rest of it. Pricing is metered at 5 credits per post RETURNED, so a member who has posted fewer than your limit costs less than you asked for, and a member with no posts costs nothing. Reposts are excluded, so every row you are charged for is one the member wrote. A profile we cannot find comes back as an empty list and costs nothing.
Request
- Base URL: https://www.socialcrawl.dev/v1
- URL: https://www.socialcrawl.dev/v1/linkedin/profile/posts/archive
- Auth: API key in header x-api-key
Query parameters
The member's LinkedIn profile URL, for example https://www.linkedin.com/in/williamhgates/.
How many posts to return, 1 to 100 (default 20). Pass 100 to walk the full archive: only a full page returns a next_cursor. You are charged 5 credits for each post actually returned, not for the limit you asked for.
The next_cursor from the previous page. Omit it for the newest posts. Native upstream cursor param. Send the universal cursor instead: the API maps it to this name for you.
Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following next_cursor, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. published_after, start_date, from_date, publish_time (yesterday, this-week, this-month, last-3-months, last-6-months) and max_age_days are accepted and applied as since.
Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. published_before, end_date and to_date are accepted and applied as until.
Universal pagination cursor. Send pagination.next_cursor from the previous response back verbatim: the API maps it to this endpoint's native pagination_token (cursor style). You never construct, decode, or look up a cursor. Omit it for page 1.
Headers
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.
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
Example response
{
"success": true,
"platform": "linkedin",
"endpoint": "/v1/linkedin/profile/posts/archive",
"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"
}
},
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoiMiIsInAiOiJwYWdlIn0",
"has_more": true,
"page_size": 30,
"stopped_at": "known_id"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.