Tickets

When using our Get tickets endpoints with a set of query params, for example ?event_id=some_event_id&ticket_status=available&stock:gt:0 to grab all the tickets for a specific event. You will notice that there are tickets that appear to be overlapping.

This is correct; we often have multiple suppliers for the 'same' tickets.

These supplier could be actual resellers, but also other customers who have decided to 'relist' their ticket on our platform.

The following fields in the ticket response are important when grouping tickets;

• event_id is the identifier of the EVENT
• category_id is the identifier of the CATEGORY
• sub_category identifies a ticket for a specific ticket validity and targetgroup (note: we currently only have regular)

The last one is a combination based on ticket_validity and ticket_targetgroup.

Note: To guarantee your clients sitting together, stick to ONE ticket_id.

Formula 1 (and other multi day events)

For multi-day events, we sometimes have tickets for specific days or the whole weekend for one category. These all share the same event_id and category_id identifiers. But they will all have their own specific sub_category

Ticket valid for	sub_category value
Friday	fri_regular
Saturday	sat_regular
Sunday	sun_regular
Saturday + Sunday	satsun_regular
Whole weekend	weekend_regular

With this knowledge, you now know you should group tickets based on:

• event_id
• category_id
• sub_category

Some combinations will have just one ticket, others might have several. Then it really depends on your (customer) needs;

• Cheapest ticket
• and/or Amount of tickets you need

For example the cheapest ticket might only have 2 left, while you need 4. Then perhaps the 2nd cheapest is a better fit.

Do remember; Each ticket_id implies a different supplier and means we cannot guarantee sitting together if you buy several tickets with different ticket_id.

How many seats are guaranteed together?

To find out, you can fetch the category information of all the categories for the whole event via: /v1/categories?event_id:some_event_id

The category_id in response can then be matched to category_id on the ticket.

This category object in the response has a party_size_together field which gives the number of seats that are guaranteed together.

Note: Yes, you can fetch each category separately but this is inefficient for bigger events due to roundtrips and latency for each call.

Football

For football, the only sub_category will be singleday_regular. Applying the same grouping as for formula 1 makes it easier and will give the proper result as well.