Much like the Event Callback, blockchain registrations for Tickets will also submit a callback to the
callbackUrl of the event, as given at the time of event creation in the Create Event step. This callback will be triggered for all Ticket actions (Create & Update).
Due to the nature of blockchain, the process of writing transaction onto chain can sometimes be difficult to predict and because of that we treat it as an asynchronous process. By offering a webhook endpoint from within your own platform it makes it east to receive blockchain information at the time of confirmation.
callbackUrl must respond to secured communication over HTTPS.
The callback is considered successful if a 200 OK is returned. In any other case, the callback server will retry to deliver the message following an exponential backoff with up to 5 attempts.