LinkedIn post date
When a LinkedIn post was published, to the millisecond, read from the number in its URL. LinkedIn shows “2w” or “3mo”; the id knows the exact moment. It runs in your browser: nothing is sent anywhere, and it is free.
The time is inside the id: nothing is sent anywhere.
How it works
Every LinkedIn post has an id: the long number after activity in its link, or after ugcPost or share in some. Its top 41 bits count the milliseconds since 1 January 1970. Shift the id right by 22 bits and you have the moment the post was made.
A post’s ugcPost or share id is made a few seconds before its activity id, so the two times can differ by that much.
The same in your own code:
// a LinkedIn post's id: its top 41 bits are milliseconds since 1970
const postDate = (id: string) => new Date(Number(BigInt(id) >> 22n));
postDate('7514393874887270401').toISOString(); // '2026-10-09T18:38:30.460Z'The rest of the post
The id gives the time and nothing else. GET /v1/linkedin/post gives the whole post: its text, author, reactions by kind, comments and reposts. A call costs 3 credits, $2.34 per 1,000 on the smallest pack, and with no key it answers from the demo. Every endpoint is on the ScrapeField LinkedIn API page.
Questions
Does it work for a deleted post?
Yes. The time is in the id, and the id stays in every link to the post, whether the post is still up or not.
Why does LinkedIn show “2w” and not the date?
LinkedIn shows a post’s age, not its date. The exact time is in the id, which is in the post’s link: copy the link from the post’s menu and paste it here.
Does it work for a comment?
A comment’s link carries its post’s id, so it gives the post’s time, not the comment’s.