Linnworks Python API Docs | dltHub
Build a Linnworks-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Linnworks is a commerce operations platform that provides a REST API to access orders, inventory, listings, and account data. The REST API base URL is https://{region}.linnworks.net/api and all requests require a session token passed in 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 add "dlt[hub]" and start loading Linnworks data in under 10 minutes.
What data can I load from Linnworks?
Here are some of the endpoints you can load from Linnworks:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| orders | /api/Orders/GetOrders | GET | Retrieves a list of orders based on various filters. | |
| processed_orders | /api/Orders/SearchProcessedOrdersPaged | GET | Search and retrieve processed orders using pagination. | |
| inventory_items | /api/Inventory/GetInventoryItems | GET | Retrieve a list of inventory items. | |
| application_profile | /api/Auth/GetApplicationProfileBySecretKey | GET | Returns application subscription profile info. | |
| auth_session | /api/Auth/AuthorizeByApplication | GET | Generates a session and returns an Authorization Token. |
How do I authenticate with the Linnworks API?
Authentication is performed by exchanging an application ID, application secret, and permanent token at the /Auth/AuthorizeByApplication endpoint to receive a session token, which must be sent in the 'Authorization' header for all subsequent requests.
1. Get your credentials
- Log in to the Linnworks Developer Portal using your Linnworks account holder email address. \n2. Navigate to the application creation section and create a new 'System Integration' application. \n3. Locate your 'Application ID' and 'Application Secret' on the application's General page. \n4. Use the provided 'Installation URL' to install the application onto your Linnworks account; this process generates a 'Permanent Token'. \n5. To perform API calls, send a POST request to https://api.linnworks.net/api/Auth/AuthorizeByApplication with your ApplicationId, ApplicationSecret, and the Token (Permanent Token). \n6. The response will return a session Token which must be included in the Authorization header for all subsequent API requests. Note: Session tokens expire after 20 minutes of inactivity.
2. Add them to .dlt/secrets.toml
[sources.linnworks_source] api_token = "REPLACE_ME"
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 Linnworks 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 linnworks_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline linnworks_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset linnworks_data The duckdb destination used duckdb:/linnworks.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 AuthorizeByApplication and GetOrders from the Linnworks 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 linnworks_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{region}.linnworks.net/api", "auth": {"type": "api_key", "api_key": api_token, "name": "Authorization"}, }, "resources": [ {"name": "orders", "endpoint": {"path": "api/Orders/GetOrders", "data_selector": "Orders"}}, {"name": "processed_orders", "endpoint": {"path": "api/Orders/SearchProcessedOrdersPaged", "data_selector": "Orders"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="linnworks_pipeline", destination="duckdb", dataset_name="linnworks_data", ) load_info = pipeline.run(linnworks_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("linnworks_pipeline").dataset() sessions_df = data.orders.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM linnworks_data.orders LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("linnworks_pipeline").dataset() data.orders.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 Linnworks 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.
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 Linnworks?
Request dlt skills, commands, AGENT.md files, and AI-native context.