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 Reseller's Bearer Token provided by Tixstock.
All Reseller 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 |
|---|---|
| Update Event | When a assigned event has been updated by Tixstock an update Webhook request is sent containing the Event Resource. Please note, Tixstock will only change an Event's date or status once it's assigned to a Reseller. |
| Cancel Event | Tixstock will send a cancelled event webhook to the resellers for the event if the event is cancelled by Tixstock. It is required that the reseller will delete all Tixstock managed listings for the event that has been cancelled. |
| Add / Update Listing | When a Broker has selected to push a Ticket to a resellers website a payload is sent with the event identifier, seat information and broker identifier. |
| Delete Listing | When a ticket is deleted by a broker within Tixstock a payload containing the reseller event identifier and user identifier is sent. |
| On Hold | When a ticket is marked as "On Hold" by another reseller a payload is sent to the remaining reseller 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 reseller to release the ticket. |
| Sold Ticket | This event will be executed when a broker ticket(s) has been sold on a different reseller site. i.e. a ticket has been uploaded to Stubhub and FanPass. The ticket is then sold on Stubhub. Tixstock will then send a Webhook event to FanPass informing them of the sale. The payload will include the event, ticket and broker identifier. |
| Order Update | When an order is updated from within Tixstock, either updating order status or adding shipping tracking ID. An update order webhook will be sent. |
| Order Fulfilment Webhooks | If an order requires fulfilment the broker can upload their tickets within Tixstock. An order fulfilment webhook is sent to the reseller containing the base64 encoded PDF and the order details it relates to.. |
| Broker Authentication | This event will be fired when a broker is linking their resellers account to an exchange on Tixstock. |
| Broker Account Open | The webhook will be executed in the event of a brokers account being opened or approved allowing the reseller to update their records. |
| Broker Account Closed | The webhook will be executed in the event of a brokers account being closed or suspended allowing the reseller to update their records. |