Murex MX.3 Python API Docs | dltHub
Build a Murex MX.3-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Murex MX.3 is a capital markets platform providing trading, risk management, and post-trade operations that exposes functionality through a REST API layer. The REST API base URL is https://api.murex.com/v1 and all requests require an OAuth 2.0 Bearer token.
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 Murex MX.3 data in under 10 minutes.
What data can I load from Murex MX.3?
Here are some of the endpoints you can load from Murex MX.3:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| orders | /orders | GET | Retrieve a list of orders | |
| instruments | /instruments | GET | Search and retrieve financial instrument reference data | |
| positions | /positions | GET | Retrieve portfolio positions | |
| reconciliations | /reconciliations | GET | items | Retrieve a list of reconciliation items |
| currencies | /reference/currencies | GET | items | Retrieve supported currencies and their configurations |
How do I authenticate with the Murex MX.3 API?
Authentication is handled via OAuth 2.0 using a Bearer token. This token must be included in the Authorization header as 'Bearer '.
1. Get your credentials
Murex MX.3 uses OAuth 2.0 for API authentication. To obtain credentials, you must access the MX.3 platform’s centralized identity management system. Depending on your organization's configuration, follow these steps: 1. Log in to your organization's Murex MX.3 client environment. 2. Navigate to the Identity Management or Security administration dashboard (specific paths vary based on your organization's deployment). 3. Request or register a service account or application client to obtain a Client ID and Client Secret. 4. Use these credentials to request a JWT bearer token via the OAuth 2.0 token endpoint provided in your specific instance's API documentation. Ensure your service account has the necessary fine-grained entitlements configured within the MX.3 role-based access control (RBAC) system.
2. Add them to .dlt/secrets.toml
[sources.murex_mx_3_source] murex_client_id = "your_client_id_here" murex_client_secret = "your_client_secret_here" murex_token_url = "https://your-mx3-instance.murex.com/oauth/token" murex_api_base_url = "https://your-mx3-instance.murex.com/v1"
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 Murex MX.3 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 murex_mx_3_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline murex_mx_3_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset murex_mx_3_data The duckdb destination used duckdb:/murex_mx_3.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 /trades and /orders from the Murex MX.3 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 murex_mx_3_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.murex.com/v1", "auth": {"type": "bearer", "token": token}, }, "resources": [ {"name": "orders", "endpoint": {"path": "orders", "data_selector": "items"}}, {"name": "trades", "endpoint": {"path": "trades", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="murex_mx_3_pipeline", destination="duckdb", dataset_name="murex_mx_3_data", ) load_info = pipeline.run(murex_mx_3_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("murex_mx_3_pipeline").dataset() sessions_df = data.orders.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM murex_mx_3_data.orders LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("murex_mx_3_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 Murex MX.3 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 Murex MX.3?
Request dlt skills, commands, AGENT.md files, and AI-native context.