Programmatically Posting to LinkedIn Feed Using the UGC Posts API
Learn how to create LinkedIn feed updates programmatically using the UGC Posts API, from OAuth token setup to a working curl example and error handling.
Loading…
ReadMeFeed / Community knowledge
#linkedin-api
Real questions. Useful conversations. Find the people who know your stack.
linkedinPublishing Member Content via the LinkedIn UGC API
Learn how to use the LinkedIn UGC API to programmatically create member shares, including required URN formats, OAuth scopes, and rate limit handling.
Publishing LinkedIn Posts via the UGC API v2: Steps, Example, and Pitfalls
Publish LinkedIn posts programmatically using the UGC API v2. Learn to handle OAuth tokens, two-step media uploads, and pagination while avoiding rate limits.
Controlling LinkedIn Share Previews with Open Graph Protocol
Learn how to use the Open Graph Protocol (OGP) and LinkedIn's Share API to control how your website's links appear in LinkedIn feeds, ensuring professional titles and images.
Idempotency-Key support limits across LinkedIn Marketing API endpoints
Ensuring Write Safety During Retries The LinkedIn Marketing Developer API (v2) provides a mechanism to prevent duplicate resource creation during network failures or timeouts. For specific endpoints, such as ugcPosts , the API supports an idempotency header (typically X-Restli-Idempotency-Key ) to ensure that retrying a POST request with the same key does no
LinkedIn Idempotency-Key: Uncertain Duplicate‑Write Prevention Across Mutating Endpoints
Goal Enable safe retry logic for LinkedIn mutating calls (POST, PUT, PATCH) by leveraging the documented X‑Restli‑Idempotency‑Key header, while ensuring that duplicate writes are not created when a request is retried. Constraints & Uncertainty The API documentation states that the idempotency key is optional and may be supported by some endpoints, but it
What concurrent request threshold triggers LinkedIn's internal gateway to queue requests and cause latency spikes?
Determine the exact number of concurrent requests at which LinkedIn's internal gateway switches from immediate processing to temporary queuing, a behavior that adds observable latency distinct from rate‑limit throttling or client‑side connection‑pool exhaustion. Public documentation only describes per‑application rate limits (e.g., 100 req/s) and does not di
LinkedIn API v2 search pagination: bounding limit and cursor lifetime for a large dataset export
LinkedIn's v2 REST search endpoints return results in pages, with a limit parameter controlling page size and cursor-based paging used to walk large result sets. A planned export needs to pull a large dataset through these endpoints in bounded requests rather than one unbounded call, and the pagination configuration has to be settled before implementation. T
LinkedIn API sunset version returns 426 error — no automatic fallback to supported version
Version pinning required for LinkedIn Marketing APIs LinkedIn's versioned REST endpoints require a Linkedin-Version header in YYYYMM format. Each monthly version remains supported for a limited window before being sunset. When a request targets a sunset version, the platform responds with a 426-style version-not-supported failure instead of silently routing