Picqer Python API Docs | dltHub

Picqer is an inventory and order management REST API. The REST API base URL is https://{your_subdomain}.picqer.com/api/v1 and All requests use HTTP Basic authentication with the API Key as the username..

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 Picqer data in under 10 minutes.

---

What data can I load from Picqer?

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

---

How do I authenticate with the Picqer API?

Picqer uses HTTP Basic authentication where the API key is sent as the username; a User-Agent header is also required on every request.

1. Get your credentials

1. Log in to your Picqer account.
2. Navigate to Settings → API.
3. Click Create new API key (or similar button).
4. Copy the generated API key; this will be used as the username for HTTP Basic authentication.
5. Store the key securely; the password field is not used.

2. Add them to .dlt/secrets.toml

Copy
[sources.picqer_inventory_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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

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

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

Copy
python picqer_inventory_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline picqer_inventory_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 products and users from the Picqer API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def picqer_inventory_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://{your_subdomain}.picqer.com/api/v1",
            "auth": {
                "type": "http_basic",
                "username": api_key,
            },
        },
        "resources": [
            {"name": "products", "endpoint": {"path": "products"}},
            {"name": "users", "endpoint": {"path": "users"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="picqer_inventory_pipeline",
        destination="duckdb",
        dataset_name="picqer_inventory_data",
    )
    load_info = pipeline.run(picqer_inventory_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):

Copy
import dlt

data = dlt.pipeline("picqer_inventory_pipeline").dataset()
sessions_df = data.products.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM picqer_inventory_data.products LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("picqer_inventory_pipeline").dataset()
data.products.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 Picqer data to?

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

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

---

Troubleshooting

Authentication Errors

• Status 401 Unauthorized – Occurs when the API key is missing, incorrect, or not sent as the HTTP Basic username. Ensure the api_key is provided and the User-Agent header is set.

Rate Limiting

• Status 429 Too Many Requests – Picqer limits requests to ~500 per minute per API key. When the limit is exceeded, the API returns a 429 response. Implement exponential back‑off or respect the Retry-After header if present.

Pagination

• Offset Pagination – GET endpoints return up to 100 records. Use the offset query parameter to retrieve subsequent pages (e.g., ?offset=100 for the second page). Continue incrementing offset until fewer than 100 records are returned.

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack