Nium Travel Python API Docs | dltHub

Build a Nium Travel-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Nium Travel API documentation details integration scenarios for online travel agents, offering APIs for virtual card management and payment processing. The main documentation covers global payment solutions, including travel, payroll, and financial services. For specific travel agency integration, refer to the API integration scenarios guide. The REST API base URL is https://gateway.nium.com/api and All requests require an API key (x-api-key) and client ID (clientHashId); Travel APIs also need a short‑lived session 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 pip install "dlt[workspace]" and start loading Nium Travel data in under 10 minutes.


What data can I load from Nium Travel?

Here are some of the endpoints you can load from Nium Travel:

ResourceEndpointMethodData selectorDescription
client_detailsclient/{clientHashId}GETRetrieve client configuration and details.
customer_detailsclient/{clientHashId}/customer/{customerHashId}GETFetch customer details including wallet information.
wallet_detailsclient/{clientHashId}/customer/{customerHashId}/wallet/{walletHashId}GETRetrieve wallet details and related payment instruments.
beneficiaries_listclient/{clientHashId}/customer/{customerHashId}/beneficiariesGETList beneficiaries for a specific customer.
remittance_statusclient/{clientHashId}/customer/{customerHashId}/wallet/{walletHashId}/remittance/{remittanceId}GETGet the status of a previously created remittance.

How do I authenticate with the Nium Travel API?

Nium uses an API key supplied as the x-api-key header and the clientHashId as a path parameter; Travel flows add a session token in the Authorization: Bearer header.

1. Get your credentials

  1. Sign up for a Nium Portal account at https://app.nium.com.\n2) After verification, open the portal and navigate to Configuration → API keys.\n3) Copy the clientHashId (Client ID) and the x‑api‑key.\n4) Use the sandbox keys for testing; request production keys from Nium Client Delivery.

2. Add them to .dlt/secrets.toml

[sources.nium_travel_source] clientHashId = "your_client_hash_id_here" x_api_key = "your_x_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:

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 Nium Travel 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 nium_travel_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline nium_travel_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 client_details and customer_details from the Nium Travel 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 nium_travel_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://gateway.nium.com/api", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "client_details", "endpoint": {"path": "client/{clientHashId}"}}, {"name": "customer_details", "endpoint": {"path": "client/{clientHashId}/customer/{customerHashId}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="nium_travel_pipeline", destination="duckdb", dataset_name="nium_travel_data", ) load_info = pipeline.run(nium_travel_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("nium_travel_pipeline").dataset() sessions_df = data.client_details.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM nium_travel_data.client_details LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("nium_travel_pipeline").dataset() data.client_details.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 Nium Travel 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 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 Nium Travel?

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