Xero Python API Docs | dltHub
Build a Xero-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Xero is a cloud‑based accounting platform that exposes accounting functions via a REST API. The REST API base URL is https://api.xero.com/api.xro/2.0 and All requests require an OAuth 2.0 Bearer token and the Xero‑tenant‑id 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 Xero data in under 10 minutes.
What data can I load from Xero?
Here are some of the endpoints you can load from Xero:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| contacts | /Contacts | GET | Contacts | Retrieve contact records |
| invoices | /Invoices | GET | Invoices | Retrieve invoice records |
| accounts | /Accounts | GET | Accounts | Retrieve chart‑of‑accounts records |
| payments | /Payments | GET | Payments | Retrieve payment records |
| bank_transactions | /BankTransactions | GET | BankTransactions | Retrieve bank transaction records |
| items | /Items | GET | Items | Retrieve item records |
| credit_notes | /CreditNotes | GET | CreditNotes | Retrieve credit note records |
| manual_journals | /ManualJournals | GET | ManualJournals | Retrieve manual journal records |
| purchase_orders | /PurchaseOrders | GET | PurchaseOrders | Retrieve purchase order records |
| prepayments | /Prepayments | GET | Prepayments | Retrieve prepayment records |
| overpayments | /Overpayments | GET | Overpayments | Retrieve overpayment records |
How do I authenticate with the Xero API?
Xero requires OAuth 2.0. Obtain an access token via the authorization code flow and send it in the Authorization: Bearer <token> header; include xero-tenant-id header for the Accounting API.
1. Get your credentials
- Log in to the Xero Developer portal (developer.xero.com).
- Click My Apps and choose New App.
- Fill in the app name, company, and redirect URI.
- After creation, note the Client ID and Client Secret displayed on the app details page.
- Configure the required scopes (e.g., accounting.transactions, accounting.settings).
- Use the client credentials in your OAuth 2.0 flow to obtain an access token.
- Store the token securely for use in API calls.
2. Add them to .dlt/secrets.toml
[sources.xero_finance_source] client_id = "your_client_id_here" client_secret = "your_client_secret_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 Xero 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 xero_finance_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline xero_finance_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset xero_finance_data The duckdb destination used duckdb:/xero_finance.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline xero_finance_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 contacts and invoices from the Xero 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 xero_finance_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.xero.com/api.xro/2.0", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "contacts", "endpoint": {"path": "Contacts", "data_selector": "Contacts"}}, {"name": "invoices", "endpoint": {"path": "Invoices", "data_selector": "Invoices"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="xero_finance_pipeline", destination="duckdb", dataset_name="xero_finance_data", ) load_info = pipeline.run(xero_finance_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("xero_finance_pipeline").dataset() sessions_df = data.contacts.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM xero_finance_data.contacts LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("xero_finance_pipeline").dataset() data.contacts.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 Xero 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
- 401 Unauthorized – Occurs when the Bearer token is missing, expired, or invalid. Refresh the access token using the OAuth flow.
- 403 Forbidden – Returned when the token lacks required scopes or the
xero-tenant-idheader is missing/incorrect.
Rate limiting
- 429 Too Many Requests – Xero imposes a limit of 60 calls per minute per tenant. Respect the
Retry-Afterheader and implement exponential back‑off.
Pagination quirks
- Use the
pagequery parameter (e.g.,?page=1) to navigate pages. The response includes aPaginationobject withpage,pageSize,pageCount, anditemCount. Ensure you iterate untilpageequalspageCount.
General errors
- 400 Bad Request – Invalid parameters or malformed request bodies.
- 500–504 Server errors – Transient issues; retry after a short delay.
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 Xero?
Request dlt skills, commands, AGENT.md files, and AI-native context.