Skip to main content
Webhooks and callbacks are essential mechanisms for the WaaS service to communicate with your application. After you set up and register callback and webhook endpoints, the WaaS service sends push messages to the designated URL when an event occurs. They allow your application to receive real-time updates or notifications and to respond to events accordingly.

​
Webhooks vs callbacks

Callbacks and webhooks serve distinct purposes within your business operations. You can view the data of all webhook events and callback messages in your organization on Cobo Portal > Developer> Webhook Events / Callback Messages.

​
Handle webhook events and callback messages

Follow the steps listed below to handle webhook events and callback messages sent from the WaaS service:
  1. Create a webhook or callback endpoint.
    • Choose a server environment.
    • Define an endpoint URL.
  2. Implement the handling logic on the server side.
    • Parse the API request.
    • Verify the signature.
    • Respond to the API request.
    • Add other handling logic (if applicable).
  3. Register the endpoint on Cobo Portal.
    When registering a webhook endpoint, you need to specify the event types to which you want to subscribe.
To create an endpoint and implement the handling logic, see Set up a callback or webhook endpoint. To register the endpoint, see Register a webhook endpoint and Register a callback endpoint. To learn more about event types and event data types, see Webhook event type and data type.

​
Notes on upgrading from WaaS 1.0 to Waas 2.0

The WaaS 1.0 service uses API callbacks for transaction notifications and withdrawal confirmations, similar to the webhooks and callbacks introduced in WaaS 2.0. The following table provides a comparison between the two versions based on the event notification mechanisms: For more details about the WaaS 1.0 callbacks, refer to How to Configure API Callback.

​
Continued use of the WaaS 1.0 API

If you choose to continue using the WaaS 1.0 API, no additional configuration is required. The existing API callbacks will function as expected.

​
Upgrade to the WaaS 2.0 API

When upgrading to WaaS 2.0, you need to do the following:
The WaaS 1.0 API callbacks use a different signature algorithm compared to the WaaS 2.0 webhooks and callbacks. Do not directly register your WaaS 1.0 endpoint on Cobo Portal. Otherwise, your endpoint will receive errors due to the differences in the signature algorithm and webhook/callback data structure between WaaS 1.0 and WaaS 2.0. Ensure you refer to the sample code provided to correctly configure your endpoint for WaaS 2.0.
If you configure both WaaS 1.0 API callbacks for transaction notifications and WaaS 2.0 webhooks, while continuing to use the WaaS 1.0 API, your endpoint will receive:
  • From WaaS 1.0: Transaction notifications.
  • From WaaS 2.0: Webhook events.