Intermittent 403 Forbidden responses when publishing to LinkedIn Company Page with valid organization scope

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 scope and is associated with an admin user guarantees successful publishing, or if LinkedIn performs additional real‑time admin role validation that can cause intermittent authorization failures even when the token appears valid.

Constraints and Uncertainty

The LinkedIn Company Page publishing API is version‑sensitive; scope names and admin role requirements may change without broad notice. Token validation includes standard OAuth checks and LinkedIn‑specific organization membership verification performed server‑side at request time, but it is not documented whether the admin role is re‑checked on each call.

To isolate the behavior, tests must be conducted in a sandbox organization using tokens with varying scopes and admin role states, comparing error codes for scope insufficiency versus role insufficiency.

Questions

• Does LinkedIn re‑validate the caller’s admin role on every publish request, or is the role checked only at token issuance?
• Can a token with the correct organization scope still receive a 403 due to a role change that occurs after the token was issued?
• What distinct error codes or error messages differentiate insufficient scope from insufficient admin role?