# LinkedIn Profile Posts Archive API (https://www.socialcrawl.dev/platforms/linkedin/profile-posts-archive)

> 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.

TL;DR: `GET /v1/linkedin/profile/posts/archive` costs 5 credits per post RETURNED. The call holds `limit x 5` up front - the default limit of 20 holds 100 and the 100 maximum holds 500 - and refunds down to the posts that actually came back, so a member with 12 posts settles at 60 credits however high `limit` was set. This is the most expensive read on the platform per row: check whether /v1/linkedin/profile/posts (5 credits up to 50 posts, 2 a post above that) already covers the window you need before walking the archive and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | yes | The member's LinkedIn profile URL, for example https://www.linkedin.com/in/williamhgates/. |
| `limit` | no | 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. |
| `pagination_token` | no | The `next_cursor` from the previous page. Omit it for the newest posts. |
| `since` | no | 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`. |
| `until` | no | 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`. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/linkedin/profile/posts/archive" \
  --data-urlencode "url=https://www.linkedin.com/in/williamhgates/" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I read a LinkedIn member's complete post history with an API?

Send a GET request to /v1/linkedin/profile/posts/archive with the member's profile URL in the url parameter, pass limit=100, and follow next_cursor until it stops coming back. This lane reads the member's own feed rather than a public search index, which is why it reaches further back than any search route.

### How far back does the LinkedIn post archive reach?

As far back as that member has posted, and the depth is a property of the member rather than a guarantee this endpoint makes. A prolific member runs to many pages, and an occasional poster finishes on the first one. We deliberately publish no headline depth figure, because a measured number read without its variance is taken as a floor. The honest signal is the cursor: when a page comes back with no next_cursor, you have everything there is.

### How much does the LinkedIn Post Archive API cost?

It is metered on the posts returned rather than per call, at 5 credits for every post that comes back. The call holds limit times that rate up front, so the maximum limit of 100 holds 500 credits, then settles down to the posts that actually arrived. A member with a dozen posts pays for a dozen however high limit was set, and a profile we cannot find comes back as an empty page and costs nothing.

### Should I use this or the LinkedIn Profile Posts endpoint?

Start with /v1/linkedin/profile/posts. It returns up to 50 posts for a flat 5 credits, more at a per-post rate up to 100, and is the whole history for most members. Come here when that window is not deep enough, or when you need what it cannot give you: an exact publish timestamp on every row, the share count, and rows written by the member rather than reshared by them.

### Are the publish dates on these posts real timestamps?

Yes. Every row carries the member's actual publish time read from the feed, which is what makes this lane safe to build a dated timeline on. The other LinkedIn feed routes derive their dates at request time, so the same post can report a slightly different date on two calls. Here it does not move.

### Why did my request come back without a next_cursor?

Because a continuation token is minted off a full page only. A limit below 100 returns that many of the newest posts and no token, since a partial page cannot be resumed without silently skipping the rest of it. Pass limit=100 whenever you intend to walk the archive, and treat a missing next_cursor on a full page as the end of the history.

### Does the LinkedIn post archive include reposts?

Reposts are excluded, so every row you are charged for is one the member wrote. That also means the count can come back lower than the number of items on their activity tab, which mixes authored posts with reshares.

See the full LinkedIn API: https://www.socialcrawl.dev/platforms/linkedin

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How to retrieve a LinkedIn member's complete post history with SocialCrawl
- How to paginate the LinkedIn post archive with next_cursor
- How much does it cost to pull a full LinkedIn post archive