LinkedIn Python API Docs | dltHub

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

Last updated:

LinkedIn offers REST API documentation for interview preparation and understanding web APIs. Essential resources include REST API interview questions and introductory tutorials on API usage. The REST API base URL is https://api.linkedin.com/v2 and OAuth 2.0 (Bearer token) required for all requests.

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 pip install "dlt[workspace]" and start loading LinkedIn data in under 10 minutes.


What data can I load from LinkedIn?

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

ResourceEndpointMethodData selectorDescription
me/v2/meGETCurrent authenticated member profile (single object)
people/v2/people/(id:{person ID})GETRetrieve another member's profile by person ID
email_addresses/v2/emailAddress?q=members&projection=(elements*(handle~))GETelementsMember email address(es) returned in elements[]
organizations/v2/organizations?q=vanityName&vanityName={name}GETelementsOrganization lookup; results in elements[]
shares/v2/shares?q=owners&owners=urn:li:person:{id}GETelementsRetrieve shares (posts); results in elements[]
ugc_posts/v2/ugcPosts?q=authors&authors=List(urn:li:person:{id})GETelementsUGC posts (user-generated content) returned in elements[]

How do I authenticate with the LinkedIn API?

LinkedIn uses OAuth 2.0; obtain an access token via the authorization code flow (POST https://www.linkedin.com/oauth/v2/accessToken) and include the token in requests using the Authorization: Bearer {ACCESS_TOKEN} header. Many endpoints also require the X-RestLi-Protocol-Version: 2.0.0 header.

1. Get your credentials

  1. Register an app at https://www.linkedin.com/developers/apps to get a Client ID and Client Secret.
  2. Configure an HTTPS redirect URI in the app settings.
  3. Direct users to https://www.linkedin.com/oauth/v2/authorization?response_type=code&client_id={CLIENT_ID}&redirect_uri={REDIRECT_URI}&scope={SCOPES} to obtain an authorization code.
  4. Exchange the code for an access token by POSTing to https://www.linkedin.com/oauth/v2/accessToken with grant_type=authorization_code, code, client_id, client_secret and redirect_uri.
  5. Use the returned access_token (Bearer) for API calls.

2. Add them to .dlt/secrets.toml

[sources.linkedin_source] token = "your_access_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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt 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:

dlt ai toolkit rest-api-pipeline install

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 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:

python linkedin_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline linkedin_pipeline 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 me and ugc_posts from the LinkedIn 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_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.linkedin.com/v2", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "me", "endpoint": {"path": "me"}}, {"name": "ugc_posts", "endpoint": {"path": "ugcPosts", "data_selector": "elements"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="linkedin_pipeline", destination="duckdb", dataset_name="linkedin_data", ) load_info = pipeline.run(linkedin_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_pipeline").dataset() sessions_df = data.me.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM linkedin_data.me LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("linkedin_pipeline").dataset() data.me.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 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 Workbench:

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

Was this page helpful?

Community Hub

Need more dlt context for LinkedIn?

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