logo
enes

HTTP connection

Last update: 5 hours ago by Irais Aguirre

HTTP connection details for the RCS inbound message and action webhook.


URLDefined by the client. The URL must be HTTPS.
MethodPOST
Typeapplication/json

Parameters

NameDescriptionType
agentIdID of the RCS agent that receives the user's message or action.Number
msisdnPhone number of the user who sends the message or performs the action. Delivered in E.164 format.String
eventIdOnly applies to user actions (make a call, open a URL, etc.). It is the unique identifier of the event; the receiver must treat the notification as a duplicate if the same eventId and msisdn pair was already sent previously.String
messageIdOnly applies to messages sent by the user. It is the unique identifier of the user's message; the receiver must treat the message as a duplicate if the same messageId and msisdn pair was already sent previously.String
eventDateDate and time, in UTC, when the message was sent or the action was performed. Value in milliseconds since January 1, 1970 00:00.Number
messageTextText written by the user.String
action.postbackDataValue of the postbackData specified when the suggested action or reply was sent to the user. This value can be used for processing and decision-making based on business rules.String
action.postbackTextText the user saw in the suggested action or reply.String
location.latLongIf the user sends a location, it is received in the format "latitude, longitude".String
file.nameIf the user sends a file, the name of that file.String
file.urlIf the user sends a file, the URL of that file.String
file.mimeTypeIf the user sends a file, the MIME type of that file.String
file.categoryIf the user sends a file, the file category. Possible values: "IMAGE","VIDEO","AUDIO".String
file.sizeIf the user sends a file, the file size in bytes.Number
RCS — Previous
Sending user messages and actions to a webhook
Next — RCS
Response