Guest data

For certain sport events we require details of the guests that are going to the event. We always try to keep this to the minimal requirements of the event organiser.

Some guest data is required the moment you make a booking, we often needs this information just to be able to buy the tickets. Depending on the organiser or supplier, this is information about the lead guest, but sometimes we need all guest information up front.

Guest Data Requirements

You can download a full overview of guest data requirements for each home team or event using the link below.

📎 Download Guest Data Overview (CSV)

Note: This list is updated daily, so make sure to check regularly for the most current requirements.

📝 Explanation of values

Condition

pre_checkout The required guest data must be provided before checkout. The booking cannot be completed without it.
pre_download You can complete the booking without guest data, but it must be provided before downloading the tickets.

Scope

all_persons The specified guest data is mandatory for all guests.
lead_guest The specified guest data is only mandatory for the lead guest.

Providing guest data

In case one or more fields have the pre_download condition, you can finalize your booking without providing those.

We will remind you by e-mail when you need to start providing the guest data. But preferablly you do this as soon as possible.

Finding guest requirements (event)

Using our API you can look-up the requirements of an event.

In the response you will get a list of the fields we require right now and for which guest (lead guest or all).

Important to note is that if pre_checkout is in the list, we require the information before we can finalize your booking.

There are a few combinations which could happen:

Combination	Meaning
`pre_checkout`, `lead_guest`	The mentioned fields are only required for the first (lead) guest, other guest data can be provided later on.
`pre_checkout`, `all_persons`	We require all mentioned fields for all the guests.
`pre_download`, `lead_guest`	The mentioned fields are only required for the first (lead) guest before you can download the tickets or we can distribute the mobile tickets. So, these fields can be supplied after the checkout process
`pre_download`, `all_persons`	We require all mentioned fields for all the guests to be supplied before you can download the tickets or we can distribute the mobile tickets. So, these fields can be supplied after the checkout process

Some events have stricter guest requirements then others. Fields you can expect and their meaning:

Field name	Description	Format
first_name	First name of the guest	string
last_name	Last name of the guest	string
contact_email	E-mail of the guest	e-mail
contact_phone	Phonenumber of the guest	string
date_of_birth	Date of birth of the guest	YYYY-MM-DD (ISO 8601)
gender	The gender of the guest	`male`,`female` or `unknown`
country_of_residence	Country of residence of the guest	country code (ISO 3166-1 alpha-3)
passport_number	Passport number of the guest	string
street_name	Streetname + housenumber of guest	string
city	City of residence of the guest	string
zip	Zipcode of the guest	string

Finding guest requirements (reservation)

Using our API, you can create a reservation using the Create reservation endpoint..

Once the reservation has been created with tickets, you can then use the Get reservation guestdata endpoint to get the guestdata and requirements for your reservation.

Based on the tickets and their quantity and guest data passed so far, you'll get a mix of guest data and 'virtual' guest data.

For example:

Reservation created
2x ticket XYZ added
Guest data provided
1x ticket XYZ added (3 total)

At this point, if you call the guestdata endpoint, you'll first get the two guest data (with guest_id filled in) that were provided. But since you requested 3 tickets totals, the other guestdata is virtual (placeholders).

Example with include_conditions=true parameter provides you with detailed information about all the fields and their conditions. It does not include fields which are not required.

json

{
  "items": [
    {
      "ticket_id": "5e8a2121a41742f8a776ee3d7a996dac_spt",
      "quantity": 3,
      "guests": [
        {
          "first_name": {
            "value": "First",
            "condition": "pre_checkout",
            "error": null
          },
          "last_name": {
            "value": "Tester",
            "condition": "pre_checkout",
            "error": null
          },
          "contact_email": {
            "value": "support@xs2event.com",
            "condition": null,
            "error": null
          },
          "date_of_birth": {
            "value": "1980-01-01",
            "condition": "pre_checkout",
            "error": null
          },
          "gender": {
            "value": "male",
            "condition": "pre_checkout",
            "error": null
          },
          "country_of_residence": {
            "value": "NLD",
            "condition": "pre_checkout",
            "error": null
          },
          "lead_guest": true,
          "guest_id": "5661e8fd160a48e18ec363cad686ba2c_gst"
        },
        {
          "first_name": {
            "value": "Second",
            "condition": "pre_checkout",
            "error": null
          },
          "last_name": {
            "value": "Tester",
            "condition": "pre_checkout",
            "error": null
          },
          "contact_email": {
            "value": "support@xs2event.com",
            "condition": null,
            "error": null
          },
          "date_of_birth": {
            "value": "1980-01-02",
            "condition": "pre_checkout",
            "error": null
          },
          "gender": {
            "value": "female",
            "condition": "pre_checkout",
            "error": null
          },
          "country_of_residence": {
            "value": "NLD",
            "condition": "pre_checkout",
            "error": null
          },
          "lead_guest": false,
          "guest_id": "808f1076ee01410882ed625abc26b907_gst"
        },
        {
          "first_name": {
            "value": null,
            "condition": "pre_checkout",
            "error": "required"
          },
          "last_name": {
            "value": null,
            "condition": "pre_checkout",
            "error": "required"
          },
          "date_of_birth": {
            "value": null,
            "condition": "pre_checkout",
            "error": "required"
          },
          "gender": {
            "value": null,
            "condition": "pre_checkout",
            "error": "required"
          },
          "country_of_residence": {
            "value": null,
            "condition": "pre_checkout",
            "error": "required"
          },
          "lead_guest": false
        }
      ]
    }
  ]
}

Example without include_conditions parameter still includes the conditions, but in a seperate field.

But this will include other guest data fields which might not be relevant for your reservation and will require more logic to process.

json

{
  "items": [
    {
      "ticket_id": "5e8a2121a41742f8a776ee3d7a996dac_spt",
      "quantity": 3,
      "guests": [
        {
          "first_name": "First",
          "last_name": "Tester",
          "passport_number": null,
          "contact_email": "support@xs2event.com",
          "contact_phone": null,
          "lead_guest": true,
          "date_of_birth": "1980-01-01",
          "gender": "male",
          "country_of_residence": "NLD",
          "guest_id": "5661e8fd160a48e18ec363cad686ba2c_gst",
          "conditions": {
            "country_of_residence": "pre_checkout",
            "date_of_birth": "pre_checkout",
            "gender": "pre_checkout",
            "first_name": "pre_checkout",
            "last_name": "pre_checkout"
          }
        },
        {
          "first_name": "Second",
          "last_name": "Tester",
          "passport_number": null,
          "contact_email": "support@xs2event.com",
          "contact_phone": null,
          "lead_guest": false,
          "date_of_birth": "1980-01-02",
          "gender": "female",
          "country_of_residence": "NLD",
          "guest_id": "808f1076ee01410882ed625abc26b907_gst",
          "conditions": {
            "country_of_residence": "pre_checkout",
            "date_of_birth": "pre_checkout",
            "gender": "pre_checkout",
            "first_name": "pre_checkout",
            "last_name": "pre_checkout"
          }
        },
        {
          "first_name": null,
          "last_name": null,
          "passport_number": null,
          "contact_email": null,
          "contact_phone": null,
          "lead_guest": false,
          "date_of_birth": null,
          "gender": null,
          "country_of_residence": null,
          "guest_id": null,
          "conditions": {
            "country_of_residence": "pre_checkout",
            "date_of_birth": "pre_checkout",
            "gender": "pre_checkout",
            "first_name": "pre_checkout",
            "last_name": "pre_checkout"
          }
        }
      ]
    }
  ]
}

Guest data ​

Guest Data Requirements ​

📝 Explanation of values ​

Condition ​

Scope ​

Providing guest data ​

Finding guest requirements (event) ​

Finding guest requirements (reservation) ​