ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #linkedin
The LinkedIn Marketing API v2 consistently returns and requires timestamps in UTC using ISO 8601 format. While the member profile provides an IANA timezone identifier via the r_liteprofile scope, this context is not propagated to analytics or campaign management endpoints. This creates day-boundary discrepancies when fetching daily performance metrics for ad
Goal Determine the maximum number of concurrent requests that a single LinkedIn access token can sustain without significant latency increase or rate‑limit errors. Constraints LinkedIn documentation lists per‑app and per‑call limits but omits a concurrent‑connection ceiling. Observed latency spikes and 429 responses appear only when multiple threads share th
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
Goal Investigate how cancelling an asynchronous LinkedIn API call via the official Java SDK affects the underlying HTTP transaction, response parsing, and connection pool usage. Constraints & Uncertainty The SDK’s asynchronous methods return a ListenableFuture that lacks a direct cancel() method, relying instead on the underlying HTTP client’s cancellati
Schema-on-Read Versioning LinkedIn's Espresso database uses a schema-on-read approach for versioned attributes to maintain backward compatibility during multi-phase rollouts. By decoupling schema changes from data migration, older application versions can coexist with newer data formats, typically because new fields are optional or carry defaults that previo
Goal: maintain repeatable LinkedIn Marketing API OAuth 2.0 authentication in a CI/CD pipeline using access and refresh tokens instead of repeated interactive logins. Uncertainty: refresh-token flow succeeds in interactive sessions but may fail in headless pipelines when LinkedIn session cookies are not preserved. The exact rejection response varies by API ve
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
Idempotency Key TTL and Atomic Commit Boundaries LinkedIn's write path uses idempotency keys stored in a distributed cache with a configurable TTL to deduplicate retried requests. The marker must be persisted atomically with the primary mutation; otherwise a race between the cache write and the database commit can allow a duplicate record when a retry arrive
LinkedIn's REST APIs utilize a date-based versioning system via the LinkedIn-Version header (formatted as YYYYMM). This mechanism ensures that partner applications remain pinned to specific API behaviors, as the platform progressively retires legacy, unversioned endpoints and deprecated version cycles. When an application sends a request without the required