IBM MQ · Rate Limits

Ibm Mq Rate Limits

IBM MQ does not publish per-second HTTP rate limits in the same way as SaaS APIs; throughput on managed MQ on Cloud is governed by the chosen reserved-capacity tier (Small / Medium / Large) and the queue manager's configured maximum channels, MQI bind connections, and message size limits. On-premises MQ throughput is bounded by the host hardware, channel definitions (MAXMSGS, SHARECNV), and queue depth settings. Limits captured here describe the documented governance surfaces rather than fabricated TPS numbers.

Ibm Mq Rate Limits is the machine-readable rate-limit profile for IBM MQ on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring varies, concurrent_connections, and bytes_per_message.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include Async, Enterprise, Integration, Messaging, and Middleware.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
AsyncEnterpriseIntegrationMessagingMiddlewareQueueRate Limiting

Limits

IBM MQ on Cloud Reserved Capacity throughput deployment
varies
governed by Small / Medium / Large reserved-capacity tier
Queue manager channel limits queue-manager
concurrent_connections
governed by queue-manager MAXCHANNELS / MAXACTIVECHANNELS / SHARECNV
Message size queue
bytes_per_message
governed by queue MAXMSGL (default 4 MB, max 100 MB)

Policies

Backoff Strategy
Clients receiving 2033 (MQRC_NO_MSG_AVAILABLE) or 2009 (MQRC_CONNECTION_BROKEN) should reconnect with exponential backoff; HTTP clients should honor 429 / 503 with exponential backoff and jitter.
Channel Heartbeats
Channels use HBINT to detect inactivity; long-running consumers should tune heartbeat and keepalive parameters to avoid spurious disconnects under load.
Capacity Sizing
For IBM MQ on Cloud, pick a Reserved Capacity tier (Small / Medium / Large) sized to peak throughput; tier upgrades are scheduled rather than instant.
Fair Use
Even on dedicated deployments, sustained traffic that materially impacts shared infrastructure may be subject to operational throttling.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/ibm-mq-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.