Share API or Open Graph: Deciding How Content Reaches LinkedIn

The Problem: Your Link Looks Wrong on LinkedIn

You publish a new engineering article and share the URL in a LinkedIn post. The preview shows the wrong title, a missing image, or your homepage logo instead of the article header. You need to know whether to fix this with HTML meta tags or with code that posts on behalf of a LinkedIn member.

Takeaway: Control the Action or Control the Preview

Use the LinkedIn Share API v2 when your application must create a post attributed to a specific authenticated member. Use Open Graph meta tags when you only need to influence how a URL looks after someone else pastes it into the LinkedIn composer.

Share API v2 Requires Server-Side OAuth

The Share API v2 lets an authorized member post a share to their network. The request needs OAuth 2.0 authorization with the w_member_social scope. The access token must be stored and used on a server; embedding it in frontend code or mobile binaries exposes it to extraction. Production use generally requires app review under the LinkedIn Developer Terms.

Calls are throttled per app and per member. LinkedIn does not publish exact limits, so your client should treat 429 Too Many Requests as a signal to back off and retry. A successful share typically returns 201 Created; missing scope returns 403 Forbidden.

Open Graph Tags Control the Link Preview Card

When any LinkedIn user pastes your public URL into a post, LinkedIn fetches the page and reads og:title, og:description, og:image, and og:url from the HTML head. No API key, app, or member consent is required.

LinkedIn caches this metadata per URL. There is no guaranteed public cache TTL or forced-refresh endpoint for arbitrary links, so changing tags may not appear immediately.

Worked Example: Fix a Broken Preview

Suppose your article lives at https://example.com/engineering-notes. Add these tags to the page's <head>:

<meta property="og:title" content="Engineering Notes: Scaling LinkedIn Previews" />
<meta property="og:description" content="A practical look at Open Graph caching and Share API limits." />
<meta property="og:image" content="https://example.com/preview.jpg" />
<meta property="og:url" content="https://example.com/engineering-notes" />

Check: Paste https://example.com/engineering-notes into the LinkedIn post composer without publishing. Confirm the card shows the intended title, description, and image. If it does not, LinkedIn may be serving a cached version of the page.

Trade-Off: Action vs. Presentation

The Share API gives you direct control over the post itself, but adds OAuth flows, secure token storage, rate-limit handling, and app review. Open Graph tags are simple to deploy but only affect the preview card; they cannot make someone post your link.

Actionable Closing

If your product needs to publish updates on a member's behalf, build the Share API v2 integration with server-side token management and exponential backoff for 429 responses. If you only want shared links to look correct, audit your public pages for complete Open Graph tags and verify them in the LinkedIn composer before relying on them.

Before implementation, read the current LinkedIn developer documentation and Developer Terms, because scopes, endpoints, and review policies can change.