Sage X3 Python API Docs | dltHub

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

Last updated:

Sage X3 provides a RESTful web service interface for managing business objects and entities like customers, sales orders, and accounting records. The REST API base URL is http://{host}:{port}/api1/ and Requests require an 'Authorization' header using either 'Basic' or 'Bearer' authentication schemes..

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


What data can I load from Sage X3?

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

ResourceEndpointMethodData selectorDescription
entities/api1/{contract}/{endpoint}/{entity}GET$resourcesRetrieve a paginated list of entity instances.
entity_details/api1/{contract}/{endpoint}/{entity}({key})GETRetrieve details for a specific entity instance.
create_entity/api1/{contract}/{endpoint}/{entity}POSTCreate a new entity instance.
update_entity/api1/{contract}/{endpoint}/{entity}({key})PUTUpdate an existing entity instance.
delete_entity/api1/{contract}/{endpoint}/{entity}({key})DELETEDelete an entity instance.

How do I authenticate with the Sage X3 API?

Authentication can be performed using Basic authentication (for on-premise) via the 'Authorization' header with 'Basic <base64_encoded_credentials>' or via OAuth2 using a 'Bearer ' token in the 'Authorization' header.

1. Get your credentials

Sage X3 supports multiple authentication methods depending on the deployment. For on-premise, you can use Basic Authentication (username/password) or Certificate Authentication. For Sage X3 Online or modern integrations, OAuth2 is the standard. To set up OAuth2, you must register your application in the Sage X3 Administration console under 'Connected applications' to obtain a Client ID and Client Secret. For Basic Authentication, ensure a dedicated web service user is configured in the Sage X3 user management settings.

2. Add them to .dlt/secrets.toml

[sources.sage_x3_source] # For Basic Authentication username = "your_web_service_user" password = "your_web_service_password" # For OAuth2 client_id = "your_client_id" client_secret = "your_client_secret" oauth2_instance = "your_oauth2_instance_name"

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 X3 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_x3_pipeline.py

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

Pipeline sage_x3_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset sage_x3_data The duckdb destination used duckdb:/sage_x3.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 $query and $details from the Sage X3 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_x3_source(auth_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://{host}:{port}/api1/", "auth": {"type": "bearer", "token": auth_token}, }, "resources": [ {"name": "entities", "endpoint": {"path": "api1/x3/{folder}/{entity}", "data_selector": "$resources"}}, {"name": "sync_api_records", "endpoint": {"path": "syracuse/collaboration/syracuse/sync/{view}", "data_selector": "rows"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sage_x3_pipeline", destination="duckdb", dataset_name="sage_x3_data", ) load_info = pipeline.run(sage_x3_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_x3_pipeline").dataset() sessions_df = data.entities.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM sage_x3_data.entities LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("sage_x3_pipeline").dataset() data.entities.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 X3 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 X3?

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