UXCam server issues a status code for every request made by its clients. The status of the response can be decoded using the table below.
| Status Code | Reason | Description |
| 200 | OK | The HTTP 200 OK success status response code indicates that the request has succeeded |
| 400 | Bad requests | This response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (for example, malformed request syntax, invalid request message framing, or deceptive request routing) |
| 401 | Unauthorized requests |
This response status code indicates that the client request has not been completed because it lacks valid authentication credentials for the requested resource. Missing valid API Key or App ID key |
| 403 | Forbidden requests | This response status code indicates that the server understands the request but refuses to authorize it |
| 404 | Resource Not Found | The requested resource doesn't exist in the server |
| 429 | Request limit exceeded | This response status code indicates the user has sent too many requests in a given amount of time |
| 500, 502, 503, 504 | Internal Server Error | These are server error response codes that indicate the server encountered an unexpected condition that prevented it from fulfilling the requests |
Rate Limiting
[status code: 429]:
This means you've made frequent calls to an API that exceeded the call rate limit. UXCam has implemented the following rate limit.
- A maximum of 10 concurrent requests per second
- A maximum of 1000 requests per hour
- A Total number of 500 records can be fetched on a single request.
If any of the above-mentioned conditions are met regarding the rate limit, then APIs will start to throw a 429 status code. Please note that this limit will only be reset every hour.
✏️ Note» To minimize rate-limiting errors, consider combining multiple filters, groupings, and aggregations into a single request to make multiple queries.