Learn about basic QuickBlox concepts to simplify the integration with QuickBlox.
Type | Privileges | Recommended to use |
---|---|---|
Authorization Key + Authorization Secret | Allows to create application/user session token | In client side code during development |
API Key | Allows to perform actions on QuickBlox server | In server side code |
Session Token Type | Description |
---|---|
Application session token | This kind of access token is needed to read the app data. Has only READ access to resources. The expiration time after the last Server API request is 2 hours. |
User session token | The user token is the most commonly used type of token. This kind of access token is needed any time the app calls an Server API to read, modify or write a specific user’s data on their behalf. Has READ/WRITE access to resources. The expiration time after the last API request is 2 hours. |
Permission | Account owner | Application user |
---|---|---|
Create user | + | + |
View user info | + | + |
Update themselves | + | + |
Update other users | + | - |
Delete themselves | + | + |
Delete other user | + | - |
Users in Call | Connections number | Per user |
---|---|---|
2 | 2 connections | 2 connections |
3 | 6 connections | 4 connections |
4 | 12 connections | 6 connections |
5 | 20 connections | 8 connections |
_id
, user_id
, parent_id
, created_at
, and updated_at
.
Allowed data types: Integer (or Array of Integer); String (or Array of String); Float (or Array of Float); Boolean (or Array of Boolean); Location (Array of [<longitude>, <latitude>]
); File; Date.
For example, you want to store a simple calendar that stores the event title and event date. In this case, you can create a Calendar class with following fields: event_title
and event_date
.
Calendar records will have the following structure:
Field name | Type |
---|---|
_id* | String |
user_id* | Integer |
parent_id* | Integer |
event_title | String |
event_date | Date |
created_at* | Integer |
updated_at* | Integer |
_id* | user_id* | parent_id* | event_title | event_date | created_at* | updated_at* |
---|---|---|---|---|---|---|
5d866b53a28f9a5ad51cb562 | 96753878 | null | Meet John | 2019-12-25T14:00:00Z | 1576629761 | 1576629761 |
5d866b53a28f9a5ad51cb563 | 96753878 | null | Visit my dentist | 2019-09-25T15:00:00Z | 1577282400 | 1577282400 |
_parent_id
field.
For example, we have the class Rating that contains score
, review
, and comment
fields. We also have a Movie class. So we can create a record of class Rating that will point to the record of the class Movie via its _parent_id
field, so the _parent_id
field will contain the ID of record from class Movie.
_parent_id
field set to the Movie class record ID) will be automatically deleted as well. _parent_id=<id_of_parent_class_record>
. Action | Description |
---|---|
Create | Create a record. |
Read | Retrieve and read the info about the chosen record. |
Update | Update any parameter for the chosen record (only those parameters that can be set by the user can be updated). |
Delete | Delete a record. |
Permission level | Description |
---|---|
Open (open) | Such permission schema means that any user within the application can access the record/records in the class and is allowed to perform an action with the current permission level. |
Owner (owner) | Owner permission level means that only Owner (a user who created a record) is allowed to perform action with the current permission level. |
Not allowed (not_allowed) | No one (except for the Account Administrator) can make a chosen action. |
Open for groups (open_for_groups) | Users having a specified tag/tags (see more info about how to set tags for the user in Users section) will be included in the group that is allowed to perform an action with the current permission level. The current permission level can consist of one or several groups (number of groups is not limited). Tags can be added/deleted in the user’s profile. |
Open for user ids (open_for_users_ids) | Only users that are specified in the permission level can make a required action with a record. One or several users can be specified (the number of users is not limited). |