Ask tech team
From QuickBlox Developers (API docs, code samples, SDK)
Jump to: navigation, search

Deprecation notice

Deprecation notice

This documentation is outdated, the newest version of the documentation is now maintained at

Error Codes

Possible API errors codes:

Code Text Description
400 Bad Request Missing or invalid parameter. Possible causes:
  • malformed request parameters
401 Unauthorized Authorization missing or incorrect. Possible causes:
  • a user tries to authorise with wrong login and password
  • a user uses invalid session token
403 Forbidden Access has been refused. Possible causes:
  • a user tries to retrieve chat messages for chat dialog he is not in occupants list.
404 Not Found The requested resource could not be found. Possible causes:
  • a user tries to retrieve chat messages for invalid chat dialog id.
  • a user tries to retrieve a custom object record with invalid id.
422 Unprocessable Entity The request was well-formed but was unable to be followed due to validation errors. Possible causes:
  • create a user with existent login or email.
  • provide values in wrong format to create some object.
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

Rate Limits

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)
Basic 80
Startup 120
Growth 160

Read more info about limits on Plans page.