Change Update - Webhooks

Change Update - Webhooks

Following feedback we are updating our webhooks for the events messageStatusUpdate, inboundMessage and messageSend.  The messageStatusUpdate and inboundMessage will include additional fields and the messageSend will now be sent on a new type =  "messageSend".

communicationActionId: this is a unique identifier for each message.
body: this is the message content.

The Message Send webhook is also changing, this will now come as a post called messageSend rather than as one of the messageStatusUpdate posts.

Message status update - if you are subscribed to the deliveryReport event you will now receive the value communicationActionID, the messageSend events will no longer come on this webhook.

{
 "type": "messageStatusUpdate",
 "conversationId": "97847",
 "communicationActionId": "220860",
 "outboundChannelAddress": "447717472695",
 "inboundChannelAddress": "WhatsApp QA Test",
 "customerUID": "",
 "dateCreated": "2021-01-28 12:22:15.397",
 "statusCode": "2"
}

Inbound Message update - if you are subscribed to the inboundMessage event you will now receive the value communicationActionID.

Inbound Message
{
 "type": "inboundMessage",
 "conversationId": "97847",
 "communicationActionId": "220859",
 "outboundChannelAddress": "447717472695",
 "inboundChannelAddress": "WhatsApp QA Test",
 "customerUID": "",
 "body": "No I don't",
 "dateCreated": "2021-01-28 12:21:28.373"
}

Message Send update - if you are subscribed to the messageSend event you will now receive a webhook post with type = messageSend.  This will contain the comunicationActionId and the body.

{
 "type": "messageSend",
 "conversationId": "97847",
 "communicationActionId": "220860",
 "outboundChannelAddress": "447717472695",
 "inboundChannelAddress": "WhatsApp QA Test",
 "customerUID": "",
 "body": "yes",
 "dateCreated": "2021-01-28 12:22:08.377",
 "statusCode": "1"
}

This change will be deployed 3rd February 2021.  

If you have any queries please contact support@webio.com

    • Related Articles

    • Webio Webhooks

      Quick trick: click into organisations, scroll down to Webhooks, click create Webhook, enter the callback URL, select the events you want to subscribe to and click create.   Some bots require data from your system in real-time.  This can be used to ...
    • Webio Webhook - What it does

      Using Webio's webhook you can configure your endpoints within your Webio organisation to post or retrieve data. Identifying the request is from us To identify the request as originating from Webio, first use the API to generate a JWT token.  Haven't ...
    • API and Webhooks

      Webio blended conversations allow you to seamlessly communicate between your clients with human or automated agents. Connecting these conversations with your internal systems provides richer conversations and slicker processes.   API Requests Using ...
    • SFTP Hooks

      You can now use Webio SFTP hooks to combine the power of webhook realtime posts and SFTP file transfers to deliver webhook calls as JSON files to your organisation's Webio SFTP folder for retrieval.   You will need to configure your Webio SFTP and ...
    • Using webhooks within your bots

      Webhooks allow you to use real time information within your Webio bots.  This can be used to provide up to date information within the conversation or to configure logic decisions within your bot based on information provided from your internal ...