RabbitMQ Management HTTP API

Introduction

Apart from this help page, all URIs will serve only resources of type application/json, and will require HTTP basic authentication (using the standard RabbitMQ user database). The default user is guest/guest.

Many URIs require the name of a virtual host as part of the path, since names only uniquely identify objects within a virtual host. As the default virtual host is called "/", this will need to be encoded as "%2f".

PUTing a resource creates it. The JSON object you upload must have certain mandatory keys (documented below) and may have optional keys. Other keys are ignored. Missing mandatory keys constitute an error.

Since bindings do not have names or IDs in AMQP we synthesise one based on all its properties. Since predicting this name is hard in the general case, you can also create bindings by POSTing to a factory URI. See the example below.

Many URIs return lists. Such URIs can have the query string parameters sort and sort_reverse added. sort allows you to select a primary field to sort by, and sort_reverse will reverse the sort order if set to true. The sort parameter can contain subfields separated by dots. This allows you to sort by a nested component of the listed items; it does not allow you to sort by more than one field. See the example below.

Examples

A few quick examples, using the Unix command line tool curl:

• Get a list of vhosts:

  $ curl -i -u guest:guest http://localhost:55672/api/vhosts
  HTTP/1.1 200 OK
  Server: MochiWeb/1.1 WebMachine/1.7 (participate in the frantic)
  Date: Tue, 31 Aug 2010 15:46:59 GMT
  Content-Type: application/json
  Content-Length: 5
  
  [{"name":"/"}]

• Get a list of channels, fast publishers first:

  $ curl -i -u guest:guest 'http://localhost:55672/api/channels?sort=message_stats.publish_details.rate&sort_reverse=true'
  HTTP/1.1 200 OK
  Server: MochiWeb/1.1 WebMachine/1.7 (participate in the frantic)
  Date: Tue, 12 Oct 2010 10:03:21 GMT
  Content-Type: application/json
  Content-Length: 6078
  Cache-Control: no-cache
  
  [{"connection_details":{"peer_address":"127.0.0.1","peer_port":47340... (remainder elided)

• Create a new vhost:

  $ curl -i -u guest:guest -H "content-type:application/json" \
    -XPUT http://localhost:55672/api/vhosts/foo
  HTTP/1.1 204 No Content
  Server: MochiWeb/1.1 WebMachine/1.7 (participate in the frantic)
  Date: Fri, 27 Aug 2010 16:56:00 GMT
  Content-Type: application/json
  Content-Length: 0

  Note: you must specify application/json as the mime type.

  Note: the name of the object is not needed in the JSON object uploaded, since it is in the URI. As a virtual host has no properties apart from its name, this means you do not need to specify a body at all!

• Create a new exchange in the default virtual host:

  $ curl -i -u guest:guest -H "content-type:application/json" \
    -XPUT -d'{"type":"direct","durable":true}' \
    http://localhost:55672/api/exchanges/%2f/my-new-exchange
  HTTP/1.1 204 No Content
  Server: MochiWeb/1.1 WebMachine/1.7 (participate in the frantic)
  Date: Fri, 27 Aug 2010 17:04:29 GMT
  Content-Type: application/json
  Content-Length: 0

  Note: we never return a body in response to a PUT or DELETE, unless it fails.

• And delete it again:

  $ curl -i -u guest:guest -H "content-type:application/json" \
    -XDELETE http://localhost:55672/api/exchanges/%2f/my-new-exchange
  HTTP/1.1 204 No Content
  Server: MochiWeb/1.1 WebMachine/1.7 (participate in the frantic)
  Date: Fri, 27 Aug 2010 17:05:30 GMT
  Content-Type: application/json
  Content-Length: 0

Reference

{"type":"direct","auto_delete":false,"durable":true,"internal":false,"arguments":[]}

{"auto_delete":false,"durable":true,"arguments":[]}

{"routing_key":"my_routing_key","arguments":[]}

{"password":"secret", "administrator":true}

{"configure":".*","write":".*","read":".*"}

{"status":"ok"}