Broker Authenticate Webhook

Tixstock API authenticates all it's webhook requests by sending a X-TIXSTOCK-SIGNATURE signature. The signature is hashed using sha256 and the data set (for the signature) is the payload of the webhook JSON encoded, which we send to your endpoint. The key is set to your Bearer Token provided by Tixstock.

All Partner endpoint's must validate the signature is correct otherwise the request should be rejected, and your endpoint should return a response with an appropriate error message and status code of 401.

Versioning

TixStock-Version header is set as part of the Webhook Headers, this outlines the version of the webhook being sent for more information on versioning please click here.

---

Tixstock Webhooks

Please note all webhook requests are sent using a POST verb.

Webhook Events	Description
On Hold	When a ticket is marked as "On Hold" by another Partner a payload is sent to the remaining Partner with the event identifier, seat information and broker identifier.
On Release	When a "On Hold" ticket has been removed from the customer basket a payload is sent to the remaining Partner to release the ticket.
Ticket Fulfillment	When a listing has been fulfilled and E-Tickets uploaded a payload is sent to the partners notifying them of the change.
Order Fulfilment Webhooks	If an order requires fulfilment the broker can upload their tickets within Tixstock. An order fulfilment webhook is sent to the Partner containing the base64 encoded PDF and the order details it relates to..

---