LinkedIn Marketing API provides comprehensive tools for managing LinkedIn advertising campaigns, enabling businesses to create, optimize, and analyze professional marketing campaigns, target B2B audiences, and measure performance across LinkedIn's professional network.
Power end-to-end data operations for your LinkedIn Marketing API with Nexla. Our bi-directional LinkedIn Marketing connector is purpose-built for LinkedIn Marketing, 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 Marketing or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your LinkedIn Marketing 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
LinkedIn Marketing uses the OAuth2 authorization code flow to securely authenticate Nexla with your LinkedIn Marketing account. No separate LinkedIn Developer Portal application or manual token exchange is required — when you create the credential in Nexla, you will be redirected to LinkedIn to sign in and grant permissions, and Nexla will automatically obtain and store the access token and refresh token needed to authenticate API requests.
The OAuth2 authorization requests scopes that provide access to LinkedIn Marketing API resources, including organization information, share statistics, and page statistics. You must sign in with a LinkedIn account that has administrator access to the organization you want to connect. The access token is sent in the Authorization: Bearer {access_token} header for all API requests to the LinkedIn Marketing API.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – LinkedIn Marketing
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
LinkedIn Marketing uses OAuth2 authentication with the authorization code flow to securely access the LinkedIn Marketing API. Click the Authorize button to begin the OAuth2 authorization flow. This will redirect you to LinkedIn's authorization page where you will be asked to sign in with your LinkedIn account and grant permissions to Nexla to access your LinkedIn Marketing data.
During the OAuth2 authorization flow, you will be redirected to LinkedIn's authorization page. You must sign in with a LinkedIn account that has access to the LinkedIn organization you want to connect. After signing in, you will be asked to grant permissions to Nexla to access your LinkedIn Marketing data. The default scopes provide access to LinkedIn Marketing API resources, including organization information, share statistics, and page statistics. Once you grant permissions, you will be redirected back to Nexla, and the authorization will be completed automatically.
After completing the OAuth2 authorization flow, Nexla will automatically obtain and store the access token and refresh token needed to authenticate API requests. The access token is used to authenticate each API request, and the refresh token is used to obtain new access tokens when the current access token expires.
OAuth2 access tokens expire after a certain period for security reasons. Nexla automatically refreshes expired access tokens using the refresh token, so you typically do not need to re-authorize unless you revoke access or the refresh token expires. The access token is sent in the Authorization: Bearer {access_token} header for all API requests to the LinkedIn Marketing API. For detailed information about LinkedIn Marketing API authentication, token management, and available endpoints, see the LinkedIn Marketing API documentation and LinkedIn OAuth2 documentation.
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.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the LinkedIn Marketing connector tile, then select the credential that will be used to connect to the LinkedIn Marketing account, and click Next; or, create a new LinkedIn Marketing credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common LinkedIn Marketing endpoints. Each template is designed specifically for the corresponding LinkedIn Marketing endpoint. 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.
Fetch My Organization Info
Fetch My Organization Info
Enter the Organization ID in the Organization ID field. This is the unique identifier for a specific organization in your LinkedIn account. The default value is "7957867". You can obtain Organization IDs from your LinkedIn account or by using other endpoints to search for organizations by vanity name or email domain.
The endpoint uses GET requests to https://api.linkedin.com/v2/organizations/{org_id} where {org_id} is the Organization ID you configured. The endpoint URL is automatically constructed based on your configuration.
The endpoint does not use pagination (iteration.type: static.url), so it will fetch a single organization record per execution. The response data path is $, which extracts the entire response object.
This endpoint uses the Organization Lookup API to find organizations that the authenticated user is an administrator of. Use other endpoints to search for organizations by vanity name or email domain.
This endpoint retrieves information about a specific organization from your LinkedIn Marketing account. The endpoint requires OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. The Organization ID identifies which organization to retrieve. The authenticated user must be an administrator of the organization to access its information. For detailed information about fetching organization information, see the LinkedIn Marketing API documentation.
Fetch Organization By Email
Fetch Organization By Email
Enter the Organization Email Domain in the Organization Email Domain field. This is the email domain associated with the organization you want to find. The default value is "nexla.com". This endpoint returns an array of organizations that match the specified email domain.
The endpoint uses GET requests to https://api.linkedin.com/v2/organizations?q=emailDomain&emailDomain={email_domain} where {email_domain} is the Organization Email Domain you configured. The endpoint URL is automatically constructed based on your configuration.
The endpoint does not use pagination (iteration.type: static.url), so it will fetch all matching organizations in a single request. The response data path is $.elements[*], which extracts all organization objects from the elements array in the API response.
This endpoint uses the Organization Lookup API to find organizations by Email Domain. Use other endpoints to search for organizations by vanity name.
This endpoint retrieves a list of organizations that match the specified email domain from your LinkedIn Marketing account. The endpoint requires OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. The email domain is used to search for matching organizations. For detailed information about fetching organizations by email domain, see the LinkedIn Marketing API documentation.
Get Organization Share Statistics: Time Range
Get Organization Share Statistics: Time Range
Enter the Organization ID in the Organization ID field. This is the unique identifier for a specific organization in your LinkedIn account. The default value is "7957867". You can obtain Organization IDs from your LinkedIn account or by using other endpoints to search for organizations.
Select the granularity of the statistics from the Granularity of the statistics pulldown menu. Available options are "DAY" or "MONTH". The default value is "DAY". This determines whether statistics are aggregated by day or by month.
Enter the start timestamp in the Start Timestamp (ms since epoch) field. This is the exclusive starting timestamp of when the query should begin. The timestamp must be in milliseconds since epoch format. You can also use Nexla macros like `{now}`, `{now-1}`, etc. The default value is `{now-1}`.
Enter the end timestamp in the End Timestamp (ms since epoch) field. This is the inclusive ending timestamp of when the query should end. The timestamp must be in milliseconds since epoch format. You can also use Nexla macros like `{now}`, `{now-1}`, etc. The default value is `{now}`.
The endpoint uses GET requests to https://api.linkedin.com/v2/organizationalEntityShareStatistics?q=organizationalEntity&organizationalEntity=urn:li:organization:{org_id}&timeIntervals.timeGranularityType={granularity}&timeIntervals.timeRange.start={start}&timeIntervals.timeRange.end={end} where {org_id}, {granularity}, {start}, and {end} are the values you configured. The endpoint URL is automatically constructed based on your configuration.
The endpoint does not use pagination (iteration.type: static.url), so it will fetch all statistics for the specified time range in a single request. The response data path is $.elements[*], which extracts all statistics objects from the elements array in the API response.
The date format is eeee with a time unit of dd (days), which is used for incremental data extraction based on record dates.
This endpoint retrieves an organization's organic share statistics for a specified time range from your LinkedIn Marketing account. The endpoint requires OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. The API returns aggregate share stats within all of the days or months in between the selected date range based on the specified granularity. The timestamps must be in milliseconds since epoch format, and you can use Nexla macros like `{now}` or `{now-1}` for dynamic date ranges. For detailed information about fetching share statistics, see the LinkedIn Marketing API documentation.
Get Organization Page Statistics: Time Range
Get Organization Page Statistics: Time Range
Enter the Organization ID in the Organization ID field. This is the unique identifier for a specific organization in your LinkedIn account. The default value is "7957867". You can obtain Organization IDs from your LinkedIn account or by using other endpoints to search for organizations.
Select the granularity of the statistics from the Granularity of the statistics pulldown menu. Available options are "DAY" or "MONTH". The default value is "DAY". This determines whether statistics are aggregated by day or by month.
Enter the start timestamp in the Start Timestamp (ms since epoch) field. This is the exclusive starting timestamp of when the query should begin. The timestamp must be in milliseconds since epoch format. You can also use Nexla macros like `{now}`, `{now-1}`, etc. The default value is `{now-1}`.
Enter the end timestamp in the End Timestamp (ms since epoch) field. This is the inclusive ending timestamp of when the query should end. The timestamp must be in milliseconds since epoch format. You can also use Nexla macros like `{now}`, `{now-1}`, etc. The default value is `{now}`.
The endpoint uses GET requests to https://api.linkedin.com/v2/organizationPageStatistics?q=organization&organization=urn:li:organization:{org_id}&timeIntervals.timeGranularityType={granularity}&timeIntervals.timeRange.start={start}&timeIntervals.timeRange.end={end} where {org_id}, {granularity}, {start}, and {end} are the values you configured. The endpoint URL is automatically constructed based on your configuration.
The endpoint does not use pagination (iteration.type: static.url), so it will fetch all statistics for the specified time range in a single request. The response data path is $.elements[*], which extracts all statistics objects from the elements array in the API response.
The date format is eeee with a time unit of dd (days), which is used for incremental data extraction based on record dates.
This endpoint retrieves statistics on views and clicks of an organization's page for a specified time range from your LinkedIn Marketing account. The endpoint requires OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. The API returns aggregate stats within all of the days or months in between the selected date range based on the specified granularity. The timestamps must be in milliseconds since epoch format, and you can use Nexla macros like `{now}` or `{now-1}` for dynamic date ranges. For detailed information about fetching page statistics, 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.
LinkedIn Marketing data sources can be manually configured to ingest data from any valid LinkedIn Marketing API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations, such as sources that use custom query parameters, different HTTP methods, or custom data transformations.
Select the format in which the data from the LinkedIn Marketing API will be received from the Content Format pulldown menu; the LinkedIn Marketing API typically returns data in JSON format. Then enter the URL of the LinkedIn Marketing API endpoint from which this source will fetch data in the Set API URL field. LinkedIn Marketing API endpoints typically follow the pattern https://api.linkedin.com/v2/{endpoint_path}. Follow the instructions in Connect to Any API to configure the remaining settings, including date/time and lookup macros, path to data, metadata, and request headers.
Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. For detailed information about LinkedIn Marketing API endpoints, authentication, and available APIs, see the LinkedIn Marketing API documentation.
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 Marketing 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.
