Create a chat message.
Create message with extra data
1. Set the ID of the dialog
Set a chat_dialog_id
to send a message to the specific dialog.
2. Type a message
Enter a message text using the message parameter.
3. Specify if you want to send a message
Set a send_to_chat
parameter to 1
to send a message to the dialog.
4. Add extra data to a message
You can extend a message with additional fields by setting key-value custom parameters.
Here, the is_pinned
is a custom parameter key and the false
is a custom parameter value.
5. As a result, the API returns a message with additional fields.
Create message in group dialog
1. Set ID of the dialog
Use a chat_dialog_id
parameter to create a message for the specific dialog.
2. Type a message
Enter a message
text using the message parameter.
3. Specify if you want to send a message
Set a send_to_chat
parameter to 1
to send a message to the dialog.
4. Specify if you want to mark messages as read/delivered
Set a markable
parameter to 1
to mark all messages as read/delivered.
5. Set message attachment
You can add an attachement to the message using the attachment
parameter.
Just specify the ID
of the file on QuickBlox server and its type
.
You can add as many attachments as you need.
6. As a result, the API returns a newly created message
Create message in private dialog
1. Set the ID of the message recipient
Use a recipient_id
parameter to set the ID of the message recipient.
2. Type a message
Enter a message text using the message
parameter.
3. As a result, the API returns a newly created message.
Create message in private dialog with API key
1. Use 'Authorization' header to pass API key
2. Use 'On-Behalf-Of' header to pass user id
To execute a request on behalf of a specific user.
3. Set the ID of the message recipient
Use a recipient_id
parameter to set the ID of the message recipient.
4. Type a message
Enter a message text using the message parameter.
5. As a result, the API returns a newly created message.
Create message with extra data and API key
1. Use 'Authorization' header to pass API key
2. Use 'On-Behalf-Of' header to pass user id
To execute a request on behalf of a specific user.
3. Set the ID of the dialog
Set a chat_dialog_id
to send a message to the specific dialog.
4. Type a message
Enter a message text using the message parameter.
5. Specify if you want to send a message
Set a send_to_chat
parameter to 1 to send a message to the dialog.
6. Add extra data to a message
You can extend a message with additional fields by setting key-value custom parameters.
Here, the is_pinned
is a custom parameter key and the false is a custom parameter value.
7. As a result, the API returns a message with additional fields.
Create message in group dialog with API key
1. Use 'Authorization' header to pass API key
2. Use 'On-Behalf-Of' header to pass user id
To execute a request on behalf of a specific user.
3. Set ID of the dialog
Use a chat_dialog_id
parameter to create a message for the specific dialog.
4. Type a message
Enter a message text using the message parameter.
5. Specify if you want to send a message
Set a send_to_chat
parameter to 1 to send a message to the dialog.
6. Specify if you want to mark messages as read/delivered
Set a markable
parameter to 1
to mark all messages as read/delivered.
7. Set message attachment
You can add an attachement to the message using the attachment
parameter.
Just specify the ID
of the file on QuickBlox server and its type
.
You can add as many attachments as you need.
8. As a result, the API returns a newly created message.
It’s possible to inject a new chat message into the chat history. In this case, this new message won’t be delivered to the recipients by XMPP real-time transport, it will be just added to the history. If you want to send a message, pass send_to_chat=1
parameter.
type=3
(PRIVATE). markable=1
to perform. Name of a custom field. Chat message can be extended with additional fields and contain any other user key-value custom parameters. Can be many 1..N.
ApiKey {your_api_key}
. Must be used either QB-Token or Authorization.201
404
An error response
Create a chat message.
Create message with extra data
1. Set the ID of the dialog
Set a chat_dialog_id
to send a message to the specific dialog.
2. Type a message
Enter a message text using the message parameter.
3. Specify if you want to send a message
Set a send_to_chat
parameter to 1
to send a message to the dialog.
4. Add extra data to a message
You can extend a message with additional fields by setting key-value custom parameters.
Here, the is_pinned
is a custom parameter key and the false
is a custom parameter value.
5. As a result, the API returns a message with additional fields.
Create message in group dialog
1. Set ID of the dialog
Use a chat_dialog_id
parameter to create a message for the specific dialog.
2. Type a message
Enter a message
text using the message parameter.
3. Specify if you want to send a message
Set a send_to_chat
parameter to 1
to send a message to the dialog.
4. Specify if you want to mark messages as read/delivered
Set a markable
parameter to 1
to mark all messages as read/delivered.
5. Set message attachment
You can add an attachement to the message using the attachment
parameter.
Just specify the ID
of the file on QuickBlox server and its type
.
You can add as many attachments as you need.
6. As a result, the API returns a newly created message
Create message in private dialog
1. Set the ID of the message recipient
Use a recipient_id
parameter to set the ID of the message recipient.
2. Type a message
Enter a message text using the message
parameter.
3. As a result, the API returns a newly created message.
Create message in private dialog with API key
1. Use 'Authorization' header to pass API key
2. Use 'On-Behalf-Of' header to pass user id
To execute a request on behalf of a specific user.
3. Set the ID of the message recipient
Use a recipient_id
parameter to set the ID of the message recipient.
4. Type a message
Enter a message text using the message parameter.
5. As a result, the API returns a newly created message.
Create message with extra data and API key
1. Use 'Authorization' header to pass API key
2. Use 'On-Behalf-Of' header to pass user id
To execute a request on behalf of a specific user.
3. Set the ID of the dialog
Set a chat_dialog_id
to send a message to the specific dialog.
4. Type a message
Enter a message text using the message parameter.
5. Specify if you want to send a message
Set a send_to_chat
parameter to 1 to send a message to the dialog.
6. Add extra data to a message
You can extend a message with additional fields by setting key-value custom parameters.
Here, the is_pinned
is a custom parameter key and the false is a custom parameter value.
7. As a result, the API returns a message with additional fields.
Create message in group dialog with API key
1. Use 'Authorization' header to pass API key
2. Use 'On-Behalf-Of' header to pass user id
To execute a request on behalf of a specific user.
3. Set ID of the dialog
Use a chat_dialog_id
parameter to create a message for the specific dialog.
4. Type a message
Enter a message text using the message parameter.
5. Specify if you want to send a message
Set a send_to_chat
parameter to 1 to send a message to the dialog.
6. Specify if you want to mark messages as read/delivered
Set a markable
parameter to 1
to mark all messages as read/delivered.
7. Set message attachment
You can add an attachement to the message using the attachment
parameter.
Just specify the ID
of the file on QuickBlox server and its type
.
You can add as many attachments as you need.
8. As a result, the API returns a newly created message.
It’s possible to inject a new chat message into the chat history. In this case, this new message won’t be delivered to the recipients by XMPP real-time transport, it will be just added to the history. If you want to send a message, pass send_to_chat=1
parameter.
type=3
(PRIVATE). markable=1
to perform. Name of a custom field. Chat message can be extended with additional fields and contain any other user key-value custom parameters. Can be many 1..N.
ApiKey {your_api_key}
. Must be used either QB-Token or Authorization.201
404
An error response