LinkedIn Pages

LinkedIn's Pages API, part of the LinkedIn Marketing API suite, exposes organization (company page) data and analytics — organization details, follower counts and demographics, and post/share engagement statistics — for pages that an authenticated administrator manages. It also supports publishing and managing organic posts on behalf of an organization page.

Power end-to-end data operations for your LinkedIn Pages API with Nexla. Our bi-directional LinkedIn Pages connector is purpose-built for LinkedIn Pages, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to LinkedIn Pages or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your LinkedIn Pages workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The LinkedIn Pages API is accessed through the LinkedIn Marketing (Community Management) APIs and is authenticated with an OAuth 2.0 access token that is sent as a Bearer token in the Authorization header. To obtain a token, you must have a LinkedIn developer application with the appropriate Marketing products enabled, and you must be an administrator of the organization page you want to work with.

1. Sign in to the LinkedIn Developer Portal and create an application, associating it with the LinkedIn Page (organization) it will manage.

2. On the application's Products tab, request access to the Community Management API (and, if you need engagement analytics such as follower and share statistics, the Marketing Developer Platform). These products require review and approval by LinkedIn before the corresponding permissions become available.

3. On the Auth tab, note your Client ID and Client Secret, and add an authorized redirect URL for your OAuth flow.

4. Complete the 3-legged OAuth 2.0 authorization code flow as an administrator of the target page to obtain an access token. Request the scopes your use case requires — for example, rw_organization_admin for reading organization data and analytics, and w_organization_social for publishing posts.

5. Copy the resulting access token. This is the value you will supply to Nexla as the API key.

Access tokens issued through the 3-legged flow expire (typically after 60 days), so plan to refresh the token before it lapses. For full details on products, permissions, and the authorization flow, see the LinkedIn Marketing API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	API key used to authenticate requests to the LinkedIn Pages API.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your LinkedIn access token in the API Key field. Nexla sends this value as a Bearer token in the Authorization header on every request to the LinkedIn Pages API, so it must be kept confidential.

   The API key is the OAuth 2.0 access token you obtained in Prerequisites. If the token is compromised or expires, generate a new one through the LinkedIn OAuth flow and update this credential.

   For more information about authentication, permissions, and available endpoints, see the LinkedIn Marketing API documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the LinkedIn Pages connector tile, then select the credential that will be used to connect to LinkedIn, and click Next; or, create a new LinkedIn Pages credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common LinkedIn Pages endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Organization Lookup

Retrieve organization lookup.

• This endpoint returns the organizations (company pages) accessible to the authenticated administrator, including the organization details you will need when configuring the analytics endpoints below.

For detailed information about organization lookups and the fields returned, see the LinkedIn Marketing API documentation.

[Rest API] List Follower Statistics

Retrieve follower statistics.

• Requires the Organization URN — the organization identifier, formatted as urn:li:organization:{id} (URL-encoded).

This endpoint returns lifetime follower statistics, including follower demographics, for the specified organization. For detailed information, see the LinkedIn Marketing API documentation.

[Rest API] List Share Statistics

Retrieve share statistics.

• Requires the Organization URN — the organization identifier, formatted as urn:li:organization:{id} (URL-encoded).

This endpoint returns lifetime share (post) engagement statistics for the specified organization. For detailed information, see the LinkedIn Marketing API documentation.

[Rest API] List Total Follower Count

Retrieve total follower count.

• This endpoint returns the total network (follower) size for an organization page.

For detailed information about network size lookups, see the LinkedIn Marketing API documentation.

[Rest API] List Follower Statistics Time Bound

Retrieve follower statistics time bound.

• Requires the Organization URN (formatted as urn:li:organization:{id}, URL-encoded) and a Time Granularity of DAY, WEEK, or MONTH.
• Provide a Time Range Start (inclusive, in milliseconds since epoch); an optional Time Range End (exclusive, in milliseconds since epoch) bounds the query window.

This endpoint returns follower statistics aggregated over a bounded time window at the requested granularity. For detailed information, see the LinkedIn Marketing API documentation.

[Rest API] List Share Statistics Time Bound

Retrieve share statistics time bound.

• Requires the Organization URN (formatted as urn:li:organization:{id}, URL-encoded) and a Time Granularity of DAY or MONTH.
• Optionally provide a Time Range Start (inclusive) and Time Range End (exclusive), both in milliseconds since epoch, to bound the query window.

This endpoint returns share (post) engagement statistics aggregated over a bounded time window at the requested granularity. For detailed information, see the LinkedIn Marketing API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

LinkedIn Pages data sources can also be manually configured to ingest data from any valid LinkedIn API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new LinkedIn Pages data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the LinkedIn Pages destination, and select the Send to Destination option from the menu. Select the LinkedIn Pages connector from the list of available destination connectors, then select the credential that will be used to connect to LinkedIn, and click Next; or, create a new LinkedIn Pages credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common LinkedIn Pages endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Post

Create an organic or sponsored post (text, image, video, article, etc.) on behalf of an organization page via the Posts API.

• Each record from your Nexset is sent as a JSON request body to create a new post. The body must match the structure expected by the LinkedIn Posts API.

For detailed information about the request body format and available post properties, see the LinkedIn Posts API documentation.

[Rest API] Update Post

Partially update an existing post's commentary, call-to-action, or lifecycle state via the Posts API.

• Requires the Post URN — the URL-encoded URN of the post to update (e.g. urn%3Ali%3Ashare%3A1234567890).

For detailed information about partial updates and the request body format, see the LinkedIn Posts API documentation.

[Rest API] Delete Post

Delete an existing post (UGC post or share) by URN via the Posts API.

• Requires the Post URN — the URL-encoded URN of the post to delete (e.g. urn%3Ali%3Ashare%3A1234567890).

For detailed information about deleting posts, see the LinkedIn Posts API documentation.

Manual configuration

LinkedIn Pages destinations can also be manually configured to send data to any valid LinkedIn API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured LinkedIn Pages endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the LinkedIn Pages endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.