

Select a product that your webhook should work with. You can turn your webhook on after clarifying all required parameters. In case you are not sure about all webhook parameters, keep the switch disabled.

A Webhook Handler is an external custom tool that processes pending objects (e.g., fulfillment requests) in Connect via the Connect API. Note that your POST request should also contains a body.Ī Webhook represents an object in Connect that triggers an external Webhook Handler through that handler’s API. The attribute value should contain a JWT (JSON Web Token) that is signed by a secret string. Such requests should contains an Authorization header with the Bearer attribute. OperationsĪ webhook calls an external handler using HTTP GET or POST requests. The webhook method avoids additional polling and consequently uses system resources more efficiently. For instance, a webhook can watch for the fulfillment queue of a particular product and trigger the specified callbacks on queue changes. Webhook: The Connect platform enables users to create a webhook for certain callbacks.For example, once a fulfillment request queue changes, the scheduled process triggers external processing system. Polling: It is possible to create a scheduled process that periodically polls a certain queue within the Connect platform.Automatic ProcessingĪn external processing system can interact with the CloudBlue Connect platform via the following methods: Consequently, the automatic processing is the best solution for such cases.
#WEBOOK CONNECTION MANUAL#
In some business cases, it is necessary to process subscriptions as fast as possible and the manual processing may prove ineffective. Therefore, Vendors are required to locate a pending fulfillment request and either approve or reject it to activate a subscription. For example, Distributors or their systems generate a new fulfillment request that should be manually processed by Vendors. Typically, one of those accounts should pay attention to a pending object and process it. In general, some workflows within the Connect platform cannot be completed until a Connect user performs certain actions.
