This documentation is outdated, the newest version of the documentation is now maintained at https://docs.quickblox.com/.
Possible API errors codes:
|400||Bad Request|| Missing or invalid parameter. Possible causes:
|401||Unauthorized|| Authorization missing or incorrect. Possible causes:
|403||Forbidden|| Access has been refused. Possible causes:
|404||Not Found|| The requested resource could not be found. Possible causes:
|422||Unprocessable Entity|| The request was well-formed but was unable to be followed due to validation errors. Possible causes:
|429||Too Many Requests||Rate limit for your current plan is exceeded|
|500||Internal Server Error||Server encountered an error, try again later|
|503||Service Unavailable||Server is at capacity, try again later|
The purpose of the rate limit is to ensure a high quality of QuickBlox service across all QuickBlox accounts, by limiting the number of API requests that an account can produce per second.
If you go over these limits when using REST based APIs, QuickBlox will start returning a HTTP 429 Too Many Requests error.
|Your membership plan||API requests per second (per account)|
Read more info about limits on Plans page.