LinkedIn API setup

Create a LinkedIn API key and publishing token.

LinkedIn calls the app identifier a Client ID, but many teams also call it an API key. For Oryginal, you need the Client ID, Client Secret, a trusted redirect URL, the right publishing scope, and an OAuth access token tied to the author you will publish as.

Before you start

What you need from LinkedIn

App credentials

  • A LinkedIn Developer app.
  • The app Client ID, also shown as the API key in some LinkedIn surfaces.
  • The app Client Secret from the Auth tab.
  • An HTTPS redirect URL that exactly matches the URL used in the OAuth request.

Publishing access

  • The w_member_social scope for member posting when it is available to your app.
  • Any organization publishing permission your LinkedIn app is approved to use.
  • The organization URN when publishing as a company page.
  • An access token generated through the same app and member flow.

LinkedIn scopes depend on the Products enabled on your app. If a scope is not available in the app Auth tab, request or enable the related LinkedIn Product before generating a token.

Developer portal steps

Create the LinkedIn app values

  1. Open the LinkedIn Developer Portal and create a new app, or select the existing app used for Oryginal.
  2. Open the Products tab and enable the LinkedIn products needed for sign-in and publishing.
  3. Open the Auth tab and copy the Client ID and Client Secret.
  4. Add the redirect URL you will use with the helper, for example https://oryginal.nomadcompass.xyz/.
  5. Confirm that the Auth tab lists the scopes you plan to request, such as openid, profile, email, and w_member_social.
Generate token

Use the Oryginal LinkedIn helper

  1. Open the LinkedIn Token Helper.
  2. Paste the Client ID and Client Secret from the LinkedIn app.
  3. Select whether the publisher is a personal profile or a company page.
  4. For a company page, paste the public company page URL, numeric organization ID, or full organization URN.
  5. Generate the OAuth link, authorize the right LinkedIn account, then paste the returned code value back into the helper.
  6. Copy the JSON result into your internal credential handoff, or copy only the access token and author URN into Oryginal.

Keep the Client Secret and access token private. The helper runs in your browser for convenience, but production token exchange should happen server-side.

Oryginal fields

Where the final values go

LinkedIn_Org_ID

Paste the author URN returned by the helper, usually urn:li:organization:12345678 for a company page.

LinkedIn_Access_Token

Paste the raw OAuth access token generated through the LinkedIn app and member authorization flow.

Official references

LinkedIn documentation used by this guide