Skip to main content
Creating a LinkedIn Developer app requires a LinkedIn Page for your company. It cannot be a member profile page, and it can’t be changed once the app is saved.

​
Creating a LinkedIn app

Register an app in the LinkedIn Developer Portal so StackOne can request access on behalf of your users.

1

Sign in to LinkedIn

Sign in to your LinkedIn Developer account.

  • Enter your LinkedIn credentials and click Sign in. LinkedIn then opens My apps.
The LinkedIn sign-in page with the Password field and Sign in button highlighted
2

Open My apps

On the My apps page, click Create app.

The LinkedIn Developer My apps page with the Create app button highlighted
3

Enter the app details

Fill in the Create an app form.

  • App name: StackOne Integration
  • In LinkedIn Page, search for and select your company’s LinkedIn Page.
  • Under App logo, click Upload a logo and choose a square image at least 100px wide.
  • Privacy policy URL is optional.
The Create an app form with the App name, LinkedIn Page and App logo fields highlighted
4

Accept the legal agreement

Under Legal agreement, select I have read and agree to these terms and click Create app.

  • LinkedIn opens the new app on its Products tab.
The Legal agreement checkbox and Create app button highlighted at the bottom of the form

​
Adding products

Products grant the OAuth scopes your app can request. This integration uses two self-serve products, plus the Advertising API for reading posts, posting as a Page and sponsored content.

1

Request Share on LinkedIn

On the Products tab, click Request access next to Share on LinkedIn.

The Products tab with the Request access button for Share on LinkedIn highlighted
2

Accept the product terms

In the Request access to Share on LinkedIn dialog, select I have read and agree to these terms and click Request access.

The Request access to Share on LinkedIn dialog with the terms checkbox and Request access button highlighted
3

Request Sign In with LinkedIn using OpenID Connect

Click Request access next to Sign In with LinkedIn using OpenID Connect, then accept the terms in the dialog the same way.

The Request access button for Sign In with LinkedIn using OpenID Connect highlighted
4

Confirm the added products

Both products now appear under Added products. Open the Auth tab.

Share on LinkedIn and Sign In with LinkedIn using OpenID Connect listed under Added products, with the Auth tab highlighted

​
Requesting the Advertising API

Required for: Batch Get Posts, Find Posts By Account, Find Posts By Authors, Get Post, Retrieve Current Member’s Profile

The actions that read posts, post as a LinkedIn Page or set sponsored content need scopes from the Advertising API product, which LinkedIn grants after reviewing your request.

  • On the Products tab, click Request access next to Advertising API and complete LinkedIn’s access request form.
  • The product grants r_basicprofile, r_organization_social and w_organization_social, among others.
  • Approved apps start on the Development tier, which allows changes to up to five ad accounts. To use an ad account on this tier, click View Ad Accounts on the Products tab, then Add Ad Account, and enter its ad account ID from Campaign Manager.
  • Posting as a Page or reading its posts also needs the connecting member to hold the ADMINISTRATOR, DIRECT_SPONSORED_CONTENT_POSTER or CONTENT_ADMIN role on that Page.
  • See Increasing access for the full access process.

​
Copying the app credentials

The Client ID and Primary Client Secret identify your app to LinkedIn during the OAuth flow.

1

Copy the Client ID and Client Secret

On the Auth tab, under Application credentials, copy both values and store them securely for use later.

  • Client ID is the public identifier of your app. Copy it from the Client ID: field and paste it into the Client ID field in the StackOne Connector profile.
  • Primary Client Secret is the app’s private key. Click the Copy icon next to it and paste it into the Client Secret field in the StackOne Connector profile.
  • Keep the secret private. Anyone who has it can request tokens for your app.
The Application credentials section with the Client ID row and the Copy icon for the Primary Client Secret highlighted

​
Configuring OAuth 2.0 settings

Register the StackOne redirect URL and check which scopes your app can request.

1

Edit the redirect URLs

Under OAuth 2.0 settings, click the pencil icon next to Authorized redirect URLs for your app.

The pencil icon next to Authorized redirect URLs for your app highlighted
2

Add the StackOne redirect URL

Click Add redirect URL, paste the StackOne redirect URL, and click Update.

  • Redirect URL: the Callback URL from your Connector Profile
The StackOne redirect URL entered in the redirect URL field with the Update button highlighted
3

Review the OAuth 2.0 scopes

Enables actions: Batch Get Documents, Batch Get Images, Batch Get Posts, Batch Get Videos, Check Status Of Upload, Complete Multi Part Upload, Create Post, Delete Post, Finalize Video Upload, Find Posts By Account, Find Posts By Authors, Get Document, Get Image, Get Post, Get Video, Initialize Document Upload, Initialize Image Upload, Initialize Video Upload, Register Upload, Retrieve Current Member’s Profile, Retrieve Member Details, Update Post, Upload Document, Upload Image

The OAuth 2.0 scopes section lists every scope your app can request. Make sure it includes the scopes this integration needs.

The saved redirect URL and the OAuth 2.0 scopes list showing openid, profile, w_member_social and email

​
Choosing the scopes to request

The Scopes field in the StackOne Connector profile sets which scopes StackOne requests when a user connects. Enter them separated by spaces, or leave the field empty to use the default.

  • Default: email openid profile w_member_social r_basicprofile r_organization_social w_organization_social
  • Only enter scopes listed under OAuth 2.0 scopes on the Auth tab. LinkedIn rejects the whole authorization if your app hasn’t been granted one of the requested scopes.
  • If your app doesn’t have the Advertising API product, enter email openid profile w_member_social instead of using the default.

​
Create the StackOne Connector Profile

1

Create a Connector Profile

Enable the connector and create a Connector Profile in your project. See Setup Connector Profile.
2

Link an Account

Once the Connector Profile is created, continue to link an account.