Anypoint MQ REST APIs

The Anypoint MQ APIs let you use REST to send and receive messages, administer queues and message exchanges, and analyze results.

Anypoint MQ provides these APIs:

Anypoint MQ Admin API
Anypoint MQ Broker API
Anypoint MQ Stats API

Anypoint MQ portals are available in the Developer portal.

Workflow for an API

The following example with the Broker API illustrates the workflow for accessing an API:

Steps:

An application sends a request to Anypoint MQ and sets how long to hold the lock on the message.
Anypoint MQ sends the message and the lock ID.
The application acknowledges the message and requests Anypoint MQ to delete the message, or the application negatively acknowledges the message and requests Anypoint MQ to make the message available to other applications. The application sends the message ID and lock ID to Anypoint MQ. For additional information on setting automatic ack or nack, see the Acknowledgment Mode guide.
If no action is taken and the duration of a lock’s time to live expires, the message is negatively acknowledged and returns to the queue to be available for other applications.

Authorize API Access

Before accessing an API, you need to acquire an access token:

Anypoint MQ Admin API - Get an access token for an Anypoint Platform user.
Anypoint MQ Broker API - Get a token from Anypoint MQ by supplying the client ID and client secret for an MQ application.
Anypoint MQ Stats API - Get an access token for an Anypoint Platform user.

The curl command for each is explained in the API sections.

Anypoint MQ Admin API

Browse queues and message exchanges
Create queues and message exchanges
Manage bindings for message exchanges

The Anypoint MQ Admin API provides access to Anypoint MQ administrative functionality.

You can get the access token from the Anypoint Platform user. The access token is also known as the Bearer. The access token has a default time to live (TTL) of 60 minutes.

You can get the organization ID and environment ID in the payload.txt file that Anypoint Platform creates for any auditable action in MQ. See MQ Audit Logging.

You can use this curl command to get the access token:

curl -X POST -H "Content-Type: application/json" -d '{"username":"USERNAME", "password":"PASSWORD"}' https://anypoint.mulesoft.com/accounts/login

The command returns output similar to:

{
  "access_token": "42424242-4242-4242-4242-424242424242",
  "token_type": "bearer",
  "redirectUrl": "/home/"
}

Admin API - Create and manage applications, queues, and message exchanges.

In the Admin API portal, click Download to download the API as a RAML, Mule 3 zipped connector file, or as a Mule 4 connector JAR file.

Create a FIFO Queue in the Admin API Portal

You can create a FIFO queue from the Admin API portal by including the "fifo": true field.

Note: The organization from which you use the Administration portal must have an Anypoint MQ FIFO entitlement. See Anypoint MQ FAQ for the regions where Anypoint MQ is available.

For the following path using the PUT operation:

/organizations/ORGANIZATION_ID/environments/ENVIRONMENT_ID/regions/REGION_ID/destinations/queues/QUEUE_ID

Use this body:

{
  "defaultTtl" : 120000,
  "defaultLockTtl" : 10000,
  "encrypted" : false,
  "fifo" : true
}

Anypoint MQ Broker API

This API lets you send and receive messages from queues and message exchanges.

The Anypoint MQ Broker API allows clients to send and receive messages from queues and exchanges.

You can get the organization ID and environment ID in the payload.txt file that Anypoint Platform creates for any auditable action in MQ. See MQ Audit Logging.

Getting the access (bearer) token requires using either a command like curl or an application like Postman. The example that follows uses curl. If you are a Windows user, you need to download a curl command before accessing the information.

The access token in this section can only be used with the Broker API. Do not use this access token with the Stats and Admin APIs.

To get the Broker API access token:

Log into Anypoint Platform.
Click MQ, Client Apps, and click the blue plus-circle icon to create an app.

Get the client ID and client secret and use these values in the curl command below replacing CLIENT_ID and CLIENT_SECRET:

curl -X POST -H "Content-Type: application/x-www-form-urlencoded" -d "client_id=CLIENT_ID&client_secret=CLIENT_SECRET&grant_type=client_credentials" "https://mq-us-east-1.anypoint.mulesoft.com/api/v1/authorize"

See the Anypoint MQ FAQ for the regions where Anypoint MQ and FIFO are available.

Submit the curl command.

The command returns output similar to:

{"access_token":"<token>","simple_client":{"envId":"ENVIRONMENT_ID","orgId":"ORGANIZATION_ID"},"token_type":"bearer"}

Broker API Portal - Publish, consume, ack, and nack messages between queues and message exchanges.

In the Broker API portal, click Download to download the API as a RAML, Mule 3 zipped connector file, or as a Mule 4 connector JAR file.

Anypoint MQ Stats API

Use cases:

Anypoint MQ metrics:
- Real time statistics for queues
- Historic statistics for queues
- Historic statistics for message exchanges
Usage metrics - View your entire organization’s usage of Anypoint MQ for billing purposes:
- Usage per environment
- Usage per organization
Browse statistics for queues and message exchanges
View the number of messages currently in a queue

For more information, see the Anypoint MQ Stats API in the MuleSoft developer portal.

Use the Anypoint MQ Stats API

To access the Anypoint MQ Stats API, you must first authenticate using the Anypoint Access Management API.

To use the Stats API, you can get the access token from the Anypoint Platform user. The access token is also known as the Bearer. The access token has a default time to live (TTL) of 60 minutes. You can get the organization ID and environment ID in the payload.txt file that Anypoint Platform creates for any auditable action in MQ. See MQ Audit Logging.

You can use this curl command to get the access token:

curl -X POST -H "Content-Type: application/json" -d '{"username":"USERNAME", "password":"PASSWORD"}' https://anypoint.mulesoft.com/accounts/login

This returns output similar to:

{
  "access_token": "42424242-4242-4242-4242-424242424242",
  "token_type": "bearer",
  "redirectUrl": "/home/"
}

Anypoint MQ Stats API - Perform statistical analysis of queue performance.

In the Stats API portal, click Download to download the API as a RAML, Mule 3 zipped connector file, or as a Mule 4 connector JAR file.

Real Time Statistics for Queues

You can get an immediate snapshot of how many messages are in the queue and how many are in-flight (see Anypoint MQ Terminology for what in-flight messages are). This data is updated in near real-time. The Statistics API can fetch real time statistics for multiple queues, and returns a comma separated list.

/queues?destinationIds={queue1},{queue2}