What is sent & how should you application respond – Tixel

You are able to configure a webhook integration for data on your ticket sales to be sent to. Once configured, we will send data to this endpoint every time a ticket for your event sells.

The data is sent in JSON format and an example of what is sent can be found below.

How to set it up

Data is sent as a POST request and is JSON formatted. The fields that are sent are:

Field	Field Type	Description
listed_at	string	The date, in UTC, that the ticket was listed
sold_at	string	The date, in UTC, that the ticket was sold
barcode	string can be null	The barcode of the ticket
price	integer	The price, in cents, that the ticket was sold at
purchase_price	integer can be null	The price, in cents, that the ticket was originally purchased from the primary platform for
type	string	The ticket type that we were able to read from the ticket
seat	string can be null	Any seating information that we were able to read on the ticket
purchase_name	string can be null	The original purchase name that we were able to read from the ticket
tags	array of strings	An array of user-selected fields that provide better clarity to the type of the ticket
order_id	string can be null	The order ID of the ticket from the primary platform
new_barcode	string can be null	When using Tixel-based, automated fulfilment, this will be the new barcode that we’ve assigned to the ticket
platform	string	The name of the primary platform for the ticket
new_name	string can be null	The new name to go on the ticket if one was required to be provided by the buyer
is_private	boolean	Indicates whether the ticket was listed publicly or privately. If it is `true` then the ticket was privately listed.
seller	object	An object containing the seller information
seller.first_name	string	The first name of the seller
seller.last_name	string	The last name of the seller
seller.email	string	The email of the seller
seller.phone	string	The phone number for the seller
seller.dob	string	The date of birth of the seller
seller.zip	string	The ZIP/post code for the seller
buyer	object	An object containing the buyer information
buyer.first_name	string	The first name of the buyer
buyer.last_name	string	The last name of the buyer
buyer.email	string	The email of the buyer
buyer.phone	string	The phone number for the buyer
buyer.dob	string	The date of birth of the buyer
buyer.zip	string	The ZIP/post code for the buyer
event	object	An object containing the event information
event.id	integer	The Tixel ID for the event
event.title	string	The title of the event on Tixel
event.starts_at	integer	The Unix timestamp for when the event starts

Sample Payload

{
    "listed_at": "2024-02-13T04:13:45.000000Z",
    "sold_at": "2024-02-13T04:14:02.000000Z",
    "barcode": "737023769786383",
    "price": 27930,
    "purchase_price": 26600,
    "type": "General Admission",
    "seat":null,
    "purchase_name":null,
    "tags": [
        "VIP"
    ],
    "order_id":null,
    "new_barcode":null,
    "platform": "Platform",
    "new_name":null,
    "seller": {
        "first_name": "Robbie",
        "last_name": "Rowe",
        "email": "christiansen.rhianna.mQhAm3sJ@yahoo.com",
        "phone": "+61474000111",
        "dob": "10/06/1989",
        "zip": "4000"
    },
    "buyer": {
        "first_name": "Sammie",
        "last_name": "Lehner",
        "email": "nathanial02.ap3XHPOV@yahoo.com",
        "phone": "+61474000222",
        "dob": "27/10/1977",
        "zip": "3000"
    },
    "event": {
        "id": 123456,
        "title": "minim elit id ipsum",
        "starts_at": 1708652159
    }
}

How should your application respond?

We need to receive a “successful” status code back to know that this was able to be received by you. A “successful” status is anything in the 2XX range.

You don’t need to provide anything in response, and anything provided will be ignored.

If we don’t receive a response, or receive a non-successful status, we will retry 2 more times with 10 minutes between each attempt.