hostid = 123456
All remaining parameters (in this case hostid) are passed to the API command being executed. In this instance we are
specifying the ID of the Wormly host to be enabled.

Note: You can supply these parameters as an HTTP POST rather than a GET request. In fact we recommend you do this, particularly
for state changing operations. Take a look at our PHP example using HTTP POST.

Wormly API Responses

Your application MUST check the HTTP Response code received in every API call. If you receive a 200 OK response, then your
API call was successful - any other response indicates failure.

In addition to the HTTP response code, WAPI returns additional information in the requested response format.
Here's what the HTTP response body would look like in our example:

{"errorcode":0}

Not a particularly exciting response; merely confirming that the operation completed without error. Note that the response is a
JSON object - had we made a request for an XML or PHP response, we would see:

Note both the 400 Bad Request HTTP response, as well as the errorcode and errormsg
properties of the response object. Had we requested a JSON or PHP response format, we would see an identical response object
expressed in those formats.

Limits

We are not currently enforcing any strict limits on your usage of the API, so you are free to do as you see fit. But
we politely ask that you behave respectfully toward our API server and don't hit it too hard. Naturally we reserve the right to introduce limits as we see fit,
and will provide you with advance notice.