Start a conversation

General (technical)

  • What file extensions are allowed?

    For security reasons only the following file extensions are allowed on the Enterprise server by default in the latest version of QuickBlox software:  gif jpeg jpg mov mp4 png csv doc docx fodg fodp fo...

  • API error types and descriptions

    In Server API documentation you can find examples of each request to the server and potential errors you may receive for a particular API request and their descriptions (e.g. for creating a session). ...

  • How do I run the QuickBlox code samples for my platform / framework?

    We provide ready-to-use chat and video calling samples to simplify the implementation and integration of QuickBlox SDKs into your applications/projects. The full list of our official code samples can ...

  • What is the difference between account user, API Users, and API application?

    An account user is an account owner, the person who registered for an account with QuickBlox. In other words, the account user is a QuickBlox customer. API Users are your end users who use the applica...

  • Is it possible to store an application session via Server API / REST?

    It is not currently possible to store an application session via Server API / REST. If the application is closed, the session will be lost and the user will need to log in again. The access via the ap...

  • How can I enable QuickBlox logs?

    We have REST API, WebRTC, and chat logging. In order to enable QuickBlox logs, please check the relevant section of our documentation: iOS SDK - Setup | iOS SDK | QuickBlox Android SDK - Setup | Andro...

  • Is it possible to add my own server logic (custom code) to QuickBlox?

    Customers can’t add custom logic to the QuickBlox Cloud server as changes will affect other customers who use the Cloud server. Enterprise customers can request implementation and deployment of custom...

  • Contacting QuickBlox Support

    Welcome to QuickBlox! We’re so glad you’ve chosen our products for your communication needs. Our chat APIs and SDKs were built with ease of integration and use in mind, but we understand that question...