IBM MQ Python API Docs | dltHub

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

Last updated:

IBM MQ REST API provides interfaces for administering MQ objects and interacting with queue managers for messaging operations. The REST API base URL is https://host:port/ibmmq/rest/v3/ and supports both HTTP Basic authentication and token-based (LTPA) authentication via cookies.

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


What data can I load from IBM MQ?

Here are some of the endpoints you can load from IBM MQ:

ResourceEndpointMethodData selectorDescription
queue_managersadmin/qmgrGETqmgrList all accessible queue managers.
queuesadmin/qmgr/{qmgrName}/queueGETqueueList queues on a queue manager.
channelsadmin/qmgr/{qmgrName}/channelGETchannelList channels on a queue manager.
subscriptionsadmin/qmgr/{qmgrName}/subscriptionGETsubscriptionList subscriptions on a queue manager.
message_listmessaging/qmgr/{qmgrName}/queue/{queueName}/messagelistGETmessagesList messages on a queue.

How do I authenticate with the IBM MQ API?

Authentication is performed via HTTP Basic (using user ID and password) or by obtaining an LTPA token cookie via the /login endpoint. State-changing operations (POST, PATCH, DELETE) additionally require the 'ibm-mq-rest-csrf-token' header, which can contain any value (including blank).

1. Get your credentials

IBM MQ does not use static API keys. Instead, you must authenticate using HTTP Basic authentication (sending a username and password) or by obtaining a token via the login resource. To enable the REST API and set up credentials, edit the mqweb server configuration in the mqwebuser.xml file. Ensure that HTTP Basic authentication is enabled within the tags. Users are defined within the local user registry or configured authentication providers. For POST, PATCH, or DELETE requests, you must also include an ibm-mq-rest-csrf-token HTTP header, which can contain any arbitrary string.

2. Add them to .dlt/secrets.toml

[sources.ibm_mq_source] mq_user = "your_username_here" mq_password = "your_password_here" mq_csrf_token = "any_arbitrary_value_string"

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 IBM MQ 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 ibm_mq_pipeline.py

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

Pipeline ibm_mq_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset ibm_mq_data The duckdb destination used duckdb:/ibm_mq.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 messaging and admin from the IBM MQ 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 ibm_mq_source(password=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://host:port/ibmmq/rest/v3/", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": password}, }, "resources": [ {"name": "queues", "endpoint": {"path": "admin/qmgr/{qmgrName}/queue", "data_selector": "queue"}}, {"name": "channels", "endpoint": {"path": "admin/qmgr/{qmgrName}/channel", "data_selector": "channel"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ibm_mq_pipeline", destination="duckdb", dataset_name="ibm_mq_data", ) load_info = pipeline.run(ibm_mq_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("ibm_mq_pipeline").dataset() sessions_df = data.queues.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM ibm_mq_data.queues LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("ibm_mq_pipeline").dataset() data.queues.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 IBM MQ 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 IBM MQ?

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