How LinkedIn Publishing Works with Postproxy
LinkedIn's publishing model
LinkedIn's API distinguishes between personal profiles and organization pages, each with different endpoints, permission scopes, and content capabilities. Publishing to an organization page requires separate OAuth authorization with the w_organization_social scope, and the API uses a UGC (User Generated Content) post format that differs from the personal share format. Postproxy abstracts this — you specify a profile ID and post content, and the API routes to the correct LinkedIn endpoint based on the account type.
Media uploads and document sharing
LinkedIn's media upload process requires registering an upload, uploading the binary to a LinkedIn-provided URL, then referencing the asset URN in your post. For images, the upload is straightforward, but videos require a chunked upload protocol with status polling. Postproxy handles the full upload lifecycle — pass media URLs in your request and the registration, upload, and asset referencing happen automatically.
Common gotchas Postproxy handles for you
LinkedIn's API has several non-obvious constraints: text posts are limited to 3,000 characters, image posts max out at 20 images, and video posts have strict codec requirements (H.264 video, AAC audio). The API also enforces rate limits per organization and returns opaque error codes when limits are hit. Postproxy validates content against these constraints before sending to LinkedIn and provides clear error messages when limits would be exceeded.
Personal profiles vs. company pages
One of the trickiest parts of LinkedIn integration is handling the difference between personal and organization posting. The API schemas, permission models, and content capabilities differ between the two. With Postproxy you connect both account types through the same OAuth flow, and the API automatically uses the correct LinkedIn endpoint and payload format based on which profile you're posting to.
