http://localhost:8888/api/v1
. To read more about configuring the HTTP listener, see HTTP Listener Configuration. You can configure a HTTP listener, or a HTTPS listener to serve the HTTP API v1.vmq-admin
CLI tool, and anything that can be done using vmq-admin
can be done using the HTTP API. Note that the HTTP API is therefore subject to any changes made to the vmq-admin
tools and their flags & options structure. All requests are performed doing a HTTP GET and if no errors occurred an HTTP 200 OK code is returned with a possible non-empty JSON payload.curl
would look like this:vmq-admin
and the HTTP API is straightforward, and if one is already familiar with how the vmq-admin
tool works, working with the API should be easy. The mapping works such that the command part of a vmq-admin
invocation is turned into a path, and the options and flags are turned into the query string.client-id
in the vmq-admin session disconnect client-id=myclient
command should be translated as: ?client-id=myclient
.--cleanup
in the vmq-admin session disconnect client-id=myclient --cleanup
command should be translated as: &--cleanup
curl
: