> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/linkedin.md).

# LinkedIn

https\://linkedin.com

{% hint style="info" %}
To publish posts as a company page, use the LinkedIn Pages connector. It needs a separate LinkedIn app, see [LinkedIn Pages](https://docs.appmixer.com/connector-configuration/linkedin-pages.md).
{% endhint %}

## OAuth app properties

| Property                | Value                                                                                                                                                                       |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multi-tenant**        | **Yes.** Any LinkedIn member can connect through one app.                                                                                                                   |
| **Vendor review**       | **None.** The connector uses *Sign In with LinkedIn using OpenID Connect* and *Share on LinkedIn*, which you add on the app's **Products** tab without a review.            |
| **Review time**         | Not applicable.                                                                                                                                                             |
| **Users before review** | No limit.                                                                                                                                                                   |
| **App owner**           | A LinkedIn member account. The app has to be associated with a LinkedIn Page; verifying the page is not needed for this connector.                                          |
| **Regions**             | One app works worldwide.                                                                                                                                                    |
| **Client secret**       | No expiry documented. An app can have two secrets at once, so you can add a new one, update the Backoffice and then delete the old one.                                     |
| **Rate limits**         | Share on LinkedIn: 100,000 requests per app and 150 requests per member per day, reset at midnight UTC. Limits of other endpoints are shown on the app's **Analytics** tab. |
| **Checked**             | 2026-11-13                                                                                                                                                                  |

**Limitations**

* LinkedIn issues refresh tokens only to approved Marketing Developer Platform partners, not to these self-serve products. The access token is valid for 60 days, then the user has to connect the account again.
* When a member authorizes the app with a different set of scopes than before, LinkedIn invalidates all of the member's earlier tokens for the app.
* Posting as a company page is not possible with this app; it needs the [LinkedIn Pages](https://docs.appmixer.com/connector-configuration/linkedin-pages.md) connector and its own app.

Sources: [3-legged OAuth flow](https://learn.microsoft.com/en-us/linkedin/shared/authentication/authorization-code-flow), [Refresh tokens](https://learn.microsoft.com/en-us/linkedin/shared/authentication/programmatic-refresh-tokens), [Share on LinkedIn](https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/share-on-linkedin), [Sign In with LinkedIn using OpenID Connect](https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin-v2), [Rate limits](https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits), [Application secret management](https://learn.microsoft.com/en-us/linkedin/shared/authentication/application-secret-management). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

### Register OAuth app

* You need to start by creating a new app on the LinkedIn Developer platform. Visit <https://developer.linkedin.com/> and log into your account. Once logged in, navigate to "MyApps", then click on "Create App". Fill in all necessary information like app name, app logo, app description, app privacy policy URL etc. You also need to fill the "Associated LinkedIn page". This is the LinkedIn page that will be associated with the app. If you don't have a LinkedIn page, you can create one by clicking on the "Create a LinkedIn Page" link.
* Navigate to the "Auth" section where you will find OAuth 2.0 settings. Here, you can set the "Authorized Redirect URLs". Take note of the application's client ID and the client secret (which should be protected as a password)

  You will need to specify the `Redirect URL` in this step.

  The `Redirect URL` should be the URL where LinkedIn will redirect the user after they authorize your app. This depends on your environment, usually in the following format: `https://api.ACME.com/auth/linkedin/callback`
* Configure scopes: Navigate to the "Products" section, request access to "Share on LinkedIn" and "Sign In with LinkedIn using OpenID Connect", once approved (it's instant approval), you will be able to see them on the top of the screen:

  ![Scopes](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-d9cf521df10a5bc296c31aae4b9a9ff8b55234c5%2Flinkedin-1.png?alt=media)

### Verification

Verification will enable scopes to be used in the LinkedIn Appmixer connector: "Advertising API", "Lead Sync API", "Conversions API" and "LinkedIn Ad Library". These scopes are not used in the current version of the LinkedIn connector, therefore it's not required. You can still perform the verification by sending the verification link generated in the "Settings" tab to the Super Admin of the page associated with the App.

Process estimated time: instant approval.

## Backoffice configuration

Configuration ID: `appmixer:linkedin` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

* `clientId` — Client ID from the *Auth* section of the LinkedIn app. Not needed when LinkedIn is authenticated through the Appmixer Auth Hub.
* `clientSecret` — Client secret from the same section. Not needed with the Auth Hub.

The same keys can be set with the CLI (`-u` updates the existing configuration instead of creating it):

```bash
appmixer service-config set appmixer:linkedin -u -d '{
  "clientId": "<client id>",
  "clientSecret": "<client secret>"
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/linkedin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
