Sage-accounting Python API Docs | dltHub

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

Last updated:

Sage Accounting is a cloud-based REST API for managing accounting entities like invoices, contacts, and bank transactions. The REST API base URL is https://api.accounting.sage.com/v3.1 and all requests require an OAuth 2.0 Bearer access token and a developer subscription key.

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


What data can I load from Sage-accounting?

Here are some of the endpoints you can load from Sage-accounting:

ResourceEndpointMethodData selectorDescription
contactscontactsGETList customers and suppliers
sales_invoicessales_invoicesGETList all sales invoices
purchase_invoicespurchase_invoicesGETList all purchase invoices
ledger_accountsledger_accountsGETList all ledger accounts
bank_accountsbank_accountsGETList all bank accounts

How do I authenticate with the Sage-accounting API?

All API requests require an Authorization header with a Bearer token, a developer subscription key in the 'ocp-apim-subscription-key' header, and a 'Content-Type: application/json' header. Some operations may also require an 'X-Site' header to identify the resource owner (business).

1. Get your credentials

  1. Navigate to the Sage Developer Portal at https://developer.sage.com/. 2. Sign up for a free developer account if you do not have one. 3. Log in to your developer dashboard. 4. Register a new application to obtain your 'Client ID' and 'Client Secret'. 5. During registration, define your 'Redirect URI' (the URL where Sage will send users after authorization). 6. Use these credentials to initiate the OAuth 2.0 authorization flow (direct users to the Sage authorization server to obtain an authorization code, then exchange it for an access token via a POST request to the token endpoint corresponding to the user's region).

2. Add them to .dlt/secrets.toml

[sources.sage_accounting_source] access_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 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 Sage-accounting 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 sage_accounting_pipeline.py

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

Pipeline sage_accounting_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset sage_accounting_data The duckdb destination used duckdb:/sage_accounting.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 api/v3/invoices and api/v3/contacts from the Sage-accounting 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 sage_accounting_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.accounting.sage.com/v3.1", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "contacts", "endpoint": {"path": "contacts"}}, {"name": "purchase_invoices", "endpoint": {"path": "purchase_invoices"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sage_accounting_pipeline", destination="duckdb", dataset_name="sage_accounting_data", ) load_info = pipeline.run(sage_accounting_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("sage_accounting_pipeline").dataset() sessions_df = data.contacts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM sage_accounting_data.contacts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("sage_accounting_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 Sage-accounting 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 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 Sage-accounting?

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

Available Pipelines