Skip to content

docs(linkedin-reshare): warn that activity id and share id can differ #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sergebulaev wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(linkedin-reshare): warn that activity id and share id can differ #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/endpoints/linkedin-reshare.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,8 +125,10 @@ Use `urn:li:share:xxx` or `urn:li:ugcPost:xxx` — **not** `urn:li:activity:xxx`
The `urn:li:activity:` URN is what appears in LinkedIn post URLs (e.g. `linkedin.com/feed/update/urn:li:activity:123`), but it is rejected by this endpoint with a 400 error.

To get the correct URN:
- For posts created via Publora, use the `postedId` field from the [get-post](get-post.md) response
- The activity ID and share ID are typically the same number — try replacing `urn:li:activity:` with `urn:li:share:` (e.g. `urn:li:activity:7451373349668282369` → `urn:li:share:7451373349668282369`)
- For posts created via Publora, use the `postedId` field from the [get-post](get-post.md) response — it is already a `share` / `ugcPost` URN, so pass it straight through.
- For any other post, prefer the post's **actual** `shareUrn` / `ugcPost` URN when you can read it (most LinkedIn post scrapers return it directly alongside the activity URN). Reach for the URL's `urn:li:activity:` id only as a fallback.

> **Caveat on the activity → share swap.** The activity id and the share/ugcPost id are *often* the same number, so replacing `urn:li:activity:` with `urn:li:share:` frequently works (e.g. `urn:li:activity:7451373349668282369` → `urn:li:share:7451373349668282369`). But they are **not guaranteed** to match — real posts exist where the activity id and the share/ugcPost id differ. When they differ, the swap yields a valid-looking URN that either reshares the wrong post or is rejected. Use the post's real `shareUrn` when you have it; treat the prefix swap as a best-effort fallback only.

## Errors

Expand Down