LinkedIn credentials

Changed in version 2.0: LinkedIn now uses OAuth 2.0 authentication. You no longer need to manually generate access tokens.

Agoras needs the following OAuth app credentials from LinkedIn to access its API:

• Client ID

• Client Secret

• Object ID (User/Organization ID)

Create a LinkedIn App

1. Sign in to the LinkedIn developer portal.

2. Click “Create app” to create a new app.

3. Enter basic details such as the app’s name and logo.

4. You will need to associate your app with a LinkedIn page. If you don’t have any pages, create one.

5. Request App Verification From the Company Page: go to the Settings tab and press the “Verify” button to receive a verification link. Open this link and confirm responsibility for the app.

Request Access to Products

1. Go to Products tab, and request access to “Share on LinkedIn” and “Sign In with LinkedIn using OpenID Connect”.

2. Once approved (usually instantly), go to the Auth tab in your app settings to find your Client ID and Client Secret.

Get App Credentials

1. In your LinkedIn App dashboard, go to the Auth tab.

2. Note your Client ID (this is your --client-id).

3. Note your Client Secret (this is your --client-secret).

Configure OAuth Redirect URI

1. In your LinkedIn App dashboard, go to the Auth tab.

2. Under “Authorized redirect URLs for your app”, add the redirect URI: https://localhost:3456/callback

Note

The redirect URI is fixed to https://localhost:3456/callback.

3. Save changes

Get Object ID (User/Organization ID)

You need the LinkedIn user or organization ID you want to post as. To find it:

1. Go to your LinkedIn profile or company page.

2. The ID can be found in the URL or by using the LinkedIn API.

3. For organizations, you can find it in the company page settings.

Alternatively, after authorizing, Agoras will automatically detect and use the correct ID.

Authorize Agoras

Once you have your app credentials, authorize Agoras to access your LinkedIn account:

agoras linkedin authorize \
  --client-id "${LINKEDIN_CLIENT_ID}" \
  --client-secret "${LINKEDIN_CLIENT_SECRET}" \
  --object-id "${LINKEDIN_OBJECT_ID}"

This will:

1. Open your browser to LinkedIn’s OAuth authorization page

2. Prompt you to grant permissions to Agoras

3. Automatically capture the authorization

4. Store encrypted credentials in ~/.agoras/tokens/

After authorization, you can use LinkedIn actions without providing tokens. Credentials are automatically refreshed when needed.

Note

Standard LinkedIn apps (for example, “Share on LinkedIn”) usually return a 60-day access token and no refresh token. Agoras stores the access token and uses it until it expires; run agoras linkedin authorize again before the 60-day window ends. Programmatic refresh tokens are only available to LinkedIn partner programs.

CI/CD Setup (Unattended Execution)

For CI/CD environments where interactive browser authorization isn’t possible, you can skip the authorize step entirely and provide all required credentials via environment variables.

1. Run agoras linkedin authorize locally first to generate credential tokens (one-time setup)

2. Extract the access or refresh token using the tokens utility command:

   # First, list tokens to find the identifier (if you don't know it)
   agoras utils tokens list --platform linkedin
   
   # Then view all stored credentials
   agoras utils tokens show --platform linkedin --identifier {identifier}
   

3. Set all required environment variables in your CI/CD pipeline:

   export LINKEDIN_OBJECT_ID="your_object_id"
   export LINKEDIN_CLIENT_ID="your_client_id"
   export LINKEDIN_CLIENT_SECRET="your_client_secret"
   # Use LINKEDIN_ACCESS_TOKEN for standard apps (expires in 60 days):
   export LINKEDIN_ACCESS_TOKEN="your_access_token_here"
   # Or use LINKEDIN_REFRESH_TOKEN for partner apps with programmatic refresh:
   export LINKEDIN_REFRESH_TOKEN="your_refresh_token_here"
   

4. Run Agoras actions directly without running authorize. All credentials will be loaded from environment variables.

Note: For unattended execution, you must provide all required credentials. The access token (or refresh token) alone is not sufficient - you also need client ID, client secret, and object ID as shown in the Platform Arguments and Environment Variables Reference documentation.

Agoras parameters

LinkedIn credential	Agoras parameter
Client ID	–client-id
Client Secret	–client-secret
Object ID (User/Org ID)	–object-id