LinkedIn Advertising Python API Docs | dltHub

Build a LinkedIn Advertising-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

The LinkedIn Marketing Solutions API allows developers to programmatically manage advertising campaigns, ad accounts, and marketing assets on LinkedIn. The REST API base URL is https://api.linkedin.com/rest/ and all requests require a Bearer token via OAuth 2.0 authorization code flow.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading LinkedIn Advertising data in under 10 minutes.


What data can I load from LinkedIn Advertising?

Here are some of the endpoints you can load from LinkedIn Advertising:

ResourceEndpointMethodData selectorDescription
ad_accountsadAccountsGETelementsRetrieve list of ad accounts.
ad_campaign_groupsadCampaignGroupsGETelementsRetrieve list of ad campaign groups.
ad_campaignsadCampaignsGETelementsRetrieve list of ad campaigns.
ad_creativesadCreativesGETelementsRetrieve list of ad creatives.
lead_form_responsesleadFormResponsesGETelementsRetrieve lead form responses.

How do I authenticate with the LinkedIn Advertising API?

All requests require an 'Authorization' header with a Bearer token. Additionally, a 'Linkedin-Version' header (format YYYYMM) is required for all versioned API calls.

1. Get your credentials

To access the LinkedIn Marketing/Advertising API, you must first register an application in the LinkedIn Developer Portal. Navigate to 'My Apps' and click 'Create App'. In the 'Products' tab of your app settings, select and apply for the 'Advertising API'. Once your application is approved by LinkedIn, you will obtain a 'Client ID' and 'Client Secret' under the 'Auth' tab of your app dashboard. Note that these credentials alone do not grant access to data; you must implement the 3-legged OAuth 2.0 flow, where an authenticated user (with appropriate ad account roles) grants consent to your application to generate an access token.

2. Add them to .dlt/secrets.toml

[sources.linkedin_advertising_source] client_id = "your_client_id_here" client_secret = "your_client_secret_here" access_token = "your_access_token_here" refresh_token = "your_refresh_token_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the LinkedIn Advertising API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python linkedin_advertising_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline linkedin_advertising_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset linkedin_advertising_data The duckdb destination used duckdb:/linkedin_advertising.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads adAccounts and adCampaigns from the LinkedIn Advertising API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def linkedin_advertising_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.linkedin.com/rest/", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "ad_campaigns", "endpoint": {"path": "adCampaigns", "data_selector": "elements"}}, {"name": "ad_creatives", "endpoint": {"path": "adCreatives", "data_selector": "elements"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="linkedin_advertising_pipeline", destination="duckdb", dataset_name="linkedin_advertising_data", ) load_info = pipeline.run(linkedin_advertising_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("linkedin_advertising_pipeline").dataset() sessions_df = data.ad_campaigns.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM linkedin_advertising_data.ad_campaigns LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("linkedin_advertising_pipeline").dataset() data.ad_campaigns.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load LinkedIn Advertising data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for LinkedIn Advertising?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines