HTTP response codes returned by the Ubidots REST API and what each status means.
When you make an HTTP request, the Ubidots REST API returns the following response codes to help you understand the request status and troubleshoot errors:
| Response Code | Description |
|---|---|
| 200 | OK -- Successful request |
| 201 | Created -- Successful request; an entity (Device or Variable) was created |
| 202 | Accepted -- The request has been accepted for processing, but processing has not been completed |
| 204 | One of the fields is incorrect, and the request was not saved -- Verify that it's a valid JSON string and that the fields are the ones expected by the endpoint (string, object, or float) |
| 400 | Bad Request -- Error due to an invalid body in your request. Verify that it's a valid JSON string and that the fields are the ones expected by the endpoint (string, object, or float) |
| 401 | Invalid API key -- Verify your API key |
| 402 | Payment Required -- Verify your balance |
| 403 | Forbidden -- This token is not valid. Verify your token |
| 404 | Not Found -- We couldn’t find the URL you're trying to access. This might be due to an incorrect device label or ID, an incorrect variable label or ID, or a typo in the request URL |
| 405 | Method Not Allowed -- This API endpoint does not accept the method used. Check our API docs to see the allowed methods |
| 415 | Unsupported Media Type -- The payload is in a format not supported by this method on the target resource |
| 420 | You have exceeded your API limits -- To upgrade your API limit, contact the Ubidots team |
| 423 | The device does not receive data because it is disabled |
| 429 | Too Many Requests -- Too many requests were sent in a given amount of time ("rate limiting") |
| 50x | Internal Error -- We're having issues with our servers. Check our status page. |