ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
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
Symptom When attempting to publish content to a LinkedIn Company Page via the official API, requests that include an OAuth 2.0 bearer token with the required organization social scope and are made by a user who is an admin of the organization sometimes return HTTP 403 Forbidden errors. Goal Determine whether a token that possesses the correct organization sc
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
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
Feature Context The UGC posts endpoint allows scheduling by supplying a UTC scheduledAt timestamp. The request body contains no field for a timezone offset or region. Current Constraint When a client constructs a local‑time datetime without timezone information, the API interprets it as UTC. This can cause unintended delays for users in regions that observe
Sign In with LinkedIn's current product issues granular OpenID Connect scopes such as openid , profile , and email , replacing legacy broad scopes like r_basicprofile that returned most member fields under a single grant. Migrating an existing integration means requesting each permission explicitly and collecting member consent per data class. The unresolved
When retrieving large datasets via the LinkedIn API, the platform implements cursor-based pagination using a start parameter to maintain stability and prevent result duplication during concurrent data updates. To manage resource consumption, the count parameter is used to bound the number of entities returned per request. However, when dealing with extremely
Ad Account Permission Hierarchy When integrating a third-party application with the LinkedIn Marketing Developer Platform, the rw_ads scope provides the necessary write access for managing sponsored updates. However, the API enforces a strict hierarchy where the application's capabilities are bounded by the authenticated user's specific role within the Linke
linkedin