How to configure and register a webhook

A step-by-step setup guide for generating a webhook in Bot Studio, registering it through the DoubleTick API, and testing it with Postman.

Webhooks allow DoubleTick to send real-time data to your systems whenever an event happens, for example when a message is sent, delivered, read, or failed. Many businesses use webhooks to automate workflows, push updates to CRM systems, store event logs, trigger notifications, or hand off data to other tools. This guide is written for first-time DoubleTick users and walks through the complete process slowly and clearly, so you can follow along confidently. No coding knowledge is required.

What's covered

• What you will need

• How to configure and register a webhook

• What you can do next

• Why webhooks are useful for businesses

• Key takeaways

• Frequently asked questions

What you will need

Before you begin, make sure you have:

• DoubleTick account with Bot Studio access

• Valid WABA (WhatsApp Business) number

• Access to Postman (or any REST API testing tool)

How to configure and register a webhook

Generate webhook credentials in Bot Studio: Open Bot Studio on DoubleTick and drag the block called On Webhook Trigger onto the workflow canvas. As soon as you add it, DoubleTick generates a Webhook URL and an Authorization Key. The Webhook URL tells DoubleTick where to send the data, and the Authorization Key makes sure only allowed systems can access the webhook. Copy both for the registration step.

Go to the webhook registration page: Open the webhook registration reference and click Register a New Webhook. Here, you are telling DoubleTick what webhook you want to use, for which WABA number, and what kind of events you want to receive.

Paste the webhook URL: In the request body, find the field named URL and paste the Webhook URL copied from Bot Studio. Normally the method here will be POST, so make sure it is set correctly.

Add the authorization header (required): This step is important because DoubleTick will not send sensitive data to an unsecured system. Go to the Headers section, click Add New Header, and enter the key Authorization with the value set to the Authorization Key from Bot Studio. This allows secure transmission of webhook data and prevents unauthorized access.

Choose the webhook event: Under Webhook Event, choose the type of data you want to receive. For example, message_status_update sends events whenever message delivery status changes. Other events may include message received, message sent, template status update, message delivered, and message read. Choose the event that matches your use case.

Enter the WABA number and name: Enter your WABA number in international format, for example +91XXXXXXXXXX. Optionally, give the webhook a name such as test_ctwa_new_6. Naming webhooks helps if you manage multiple business numbers or workflows.

Generate and copy the cURL command: Once all details are filled, click Generate cURL and copy the cURL command that appears on screen. This command is what you will use to register the webhook via Postman.

Import the cURL command into Postman: Open the Postman application, click Import, paste the cURL command in the import box, and click Continue. Postman creates a new request based on the cURL and shows you the body, headers, and endpoint.

Adjust authorization in Postman: Postman often adds Basic Authorization automatically, but DoubleTick does not require this for webhook registration. Go to the Authorization tab and remove Basic Auth. Do not add anything else here, since the Authorization Key in headers is enough.

Test the webhook registration: Click Send. If everything is correct, you should receive 200 OK, which means the webhook has been successfully registered.

Verify the webhook in DoubleTick: Go to DoubleTick, open Settings → Webhooks, and look for the webhook name you created, for example test_ctwa_new_6. If it appears, your setup is complete.

Trigger the webhook (test event): Since this example used message_status_update, the webhook triggers when message delivery status changes. To test it, open any chat in DoubleTick, send a test message, and wait until the message receives status ticks such as Sent, Delivered, and Read. When the status updates, DoubleTick sends data to your webhook. In Bot Studio, click Capture Response, and you should see structured JSON data appear.

What you can do next

Once the webhook data is captured, you can trigger automation, build conditions, push data to CRMs, log delivery events, notify internal systems, and connect with third-party tools. This is where webhook-based automation becomes powerful.

Why webhooks are useful for businesses

Webhooks help automate workflows such as:

• Updating lead stages

• Notifying sales teams

• Tracking message success

• Measuring campaign performance

• Storing delivery logs

• Triggering workflows in Bot Studio

Without webhooks, these tasks must be done manually.

Key takeaways

• Setting up a webhook has two parts: generating credentials in Bot Studio and registering the URL through the DoubleTick API using Postman

• The Authorization Key must be added as a header, and Postman's default Basic Auth should be removed

• A successful registration returns 200 OK, and the webhook then appears under Settings → Webhooks in DoubleTick

• Testing with a real message helps confirm the webhook is capturing structured JSON data correctly

Frequently asked questions

Do I need coding knowledge to set up a webhook?

No. This guide only needs Bot Studio, the DoubleTick API docs page, and Postman. No coding is required.

Why do I need to add the Authorization Key as a header?

DoubleTick will not send sensitive data to an unsecured system, so the Authorization Key confirms that only allowed systems can receive the webhook data.

What does a 200 OK response mean when testing the webhook?

It means the webhook has been registered successfully with DoubleTick.

Why does Postman add Basic Auth automatically, and should I keep it?

Postman sometimes adds Basic Authorization by default when importing a cURL command, but DoubleTick does not need it for webhook registration. You should remove it and rely only on the Authorization Key header.

How do I confirm my webhook is actually working after registration?

Send a test message in DoubleTick and watch for status ticks such as Sent, Delivered, and Read. If the webhook is working, DoubleTick sends data for each status change, which you can view using Capture Response in Bot Studio.

Related articles

How to Use Webhooks to Pass Events to Third-PartyHow to use Message Status Update WebhookHow to use Message Received Webhook