Linear Python API Docs | dltHub
Build a Linear-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Linear is a platform whose public API is built using GraphQL. The REST API base URL is https://api.linear.app/graphql and All requests require an API key for authentication, supplied via the Authorization header..
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 Linear data in under 10 minutes.
What data can I load from Linear?
Here are some of the endpoints you can load from Linear:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
issues | /graphql | POST | issues.nodes | Get a list of issues |
issue | /graphql | POST | issue | Get a single issue by ID |
teams | /graphql | POST | teams.nodes | Get a list of teams |
team | /graphql | POST | team | Get a single team by ID |
users | /graphql | POST | users.nodes | Get a list of users |
How do I authenticate with the Linear API?
Authentication is done using API keys. The API key should be included in the Authorization header of each request.
1. Get your credentials
- Log in to your Linear account.
- Navigate to 'Settings'.
- Go to 'Account > Security & Access'.
- Create a new personal API key.
2. Add them to .dlt/secrets.toml
[sources.linear_source] api_key = "your_api_key_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 Linear 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 linear_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline linear_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset linear_data The duckdb destination used duckdb:/linear.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline linear_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 issues and teams from the Linear 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 linear_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.linear.app/graphql", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "issues", "endpoint": {"path": "graphql", "data_selector": "issues.nodes"}}, {"name": "teams", "endpoint": {"path": "graphql", "data_selector": "teams.nodes"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="linear_pipeline", destination="duckdb", dataset_name="linear_data", ) load_info = pipeline.run(linear_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("linear_pipeline").dataset() sessions_df = data.issues.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM linear_data.issues LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("linear_pipeline").dataset() data.issues.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 Linear data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
Troubleshooting
Authentication Errors
If you encounter 401 or 403 errors, it typically indicates invalid credentials or insufficient permissions for the API key being used. Ensure your API key is correctly configured in your Linear settings and has the necessary access rights.
Rate Limiting
The Linear API may impose rate limits. If you receive 429 errors, it means you have exceeded the allowed number of requests within a given timeframe. Implement exponential backoff or reduce your request frequency to avoid hitting these limits.
Malformed Requests
400 or 500 errors can occur due to malformed GraphQL queries or invalid request bodies. Double-check your query syntax, variables, and ensure they conform to the GraphQL schema defined by Linear.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 Linear?
Request dlt skills, commands, AGENT.md files, and AI-native context.