• The definitions are merged. Anything already existing on the server but not in the uploaded definitions is untouched.
• Conflicting definitions on immutable objects (exchanges, queues and bindings) will be ignored. The existing definition will be preserved.
• Conflicting definitions on mutable objects will cause the object in the server to be overwritten with the object from the definitions.
• In the event of an error you will be left with a part-applied set of definitions.

• The definitions are merged. Anything already existing on the server but not in the uploaded definitions is untouched.
• Conflicting definitions on immutable objects (exchanges, queues and bindings) will be ignored. The existing definition will be preserved.
• Conflicting definitions on mutable objects will cause the object in the server to be overwritten with the object from the definitions.
• In the event of an error you will be left with a part-applied set of definitions.

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

When DELETEing an exchange you can add the query string parameter if-unused=true. This prevents the delete from succeeding if the exchange is bound to a queue or as a source to another exchange.

{"properties":{},"routing_key":"my key","payload":"my body","payload_encoding":"string"}

{"routed": true}

Please note that the HTTP API is not ideal for high performance publishing; the need to create a new TCP connection for each message published can limit message throughput compared to AMQP or other protocols using long-lived connections.

{"auto_delete":false,"durable":true,"arguments":{},"node":"rabbit@smacmullen"}

When DELETEing a queue you can add the query string parameters if-empty=true and / or if-unused=true. These prevent the delete from succeeding if the queue contains messages, or has consumers, respectively.

{"action":"sync"}

{"count":5,"ackmode":"ack_requeue_true","encoding":"auto","truncate":50000}

• count controls the maximum number of messages to get. You may get fewer messages than this if the queue cannot immediately provide them.
• ackmode determines whether the messages will be removed from the queue. If ackmode is ack_requeue_true or reject_requeue_true they will be requeued - if ackmode is ack_requeue_false or reject_requeue_false they will be removed.
• encoding must be either "auto" (in which case the payload will be returned as a string if it is valid UTF-8, and base64 encoded otherwise), or "base64" (in which case the payload will always be base64 encoded).
• If truncate is present it will truncate the message payload if it is larger than the size given (in bytes).

truncate is optional; all other keys are mandatory.

Please note that the get path in the HTTP API is intended for diagnostics etc - it does not implement reliable delivery and so should be treated as a sysadmin's tool rather than a general API for messaging.

A list of all bindings between an exchange and a queue. Remember, an exchange and a queue can be bound together many times!

To create a new binding, POST to this URI. Request body should be a JSON object optionally containing two fields, routing_key (a string) and arguments (a map of optional arguments):

{"routing_key":"my_routing_key", "arguments":{"x-arg": "value"}}

A list of all bindings between two exchanges, similar to the list of all bindings between an exchange and a queue, above.

To create a new binding, POST to this URI. Request body should be a JSON object optionally containing two fields, routing_key (a string) and arguments (a map of optional arguments):

{"routing_key":"my_routing_key", "arguments":{"x-arg": "value"}}

{"description":"virtual host description", "tags":"accounts,production"}

{"tracing":true}

{"users" : ["user1", "user2", "user3"]}

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

{"password_hash":"2lmoth8l4H0DViLaK9Fxi6l9ds8=", "tags":"administrator"}

{"value": 100}

curl -4u 'guest:guest' -H 'content-type:application/json' -X PUT localhost:15672/api/user-limits/guest/max-connections -d '{"value": 50}'

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

{"exchange":"amq.topic","write":"^a","read":".*"}

{"vhost": "/","component":"federation","name":"local_username","value":"guest"}

{"name":"user_vhost_mapping","value":{"guest":"/","rabbit":"warren"}}

{"pattern":"^amq.", "definition": {"federation-upstream-set":"all"}, "priority":0, "apply-to": "all"}

{"pattern":"^amq.", "definition": {"expires":100}, "priority":0, "apply-to": "queues"}

Checks the expiration date on the certificates for every listener configured to use TLS. Responds a 200 OK if all certificates are valid (have not expired), otherwise responds with a 503 Service Unavailable.

Valid units: days, weeks, months, years. The value of the within argument is the number of units. So, when within is 2 and unit is "months", the expiration period used by the check will be the next two months.

{"value": 100}

curl -4u 'guest:guest' -H 'content-type:application/json' -X PUT localhost:15672/api/vhost-limits/my-vhost/max-connections -d '{"value": 50}'

{"oauth_enabled":"boolean", "oauth_client_id":"string", "oauth_provider_url":"string"}

curl -4u 'guest:guest' -XPOST localhost:15672/api/rebalance/queues/