When selling into events with limited capacities, we strongly recommend you reserve the capacity in the event as soon as the user selects and adds tickets to the cart. This reservation will ensure the tickets are still available when the user completes the purchase. Without creating a reservation, you run the risk of the event being sold out between the time you add tickets to the cart and complete checkout.
If you primarily sell General Admission tickets, or tickets where selling out would never be an issue, the reservation feature may not be beneficial to you. In that case, you don’t need to implement it in your purchase flow.
The following endpoints are used to create, update/maintain, and delete report definitions. For more information about ACME report definitions, including information about query types and available fields, please review the ACME Reporting documentation.
TABLE OF CONTENTS |
Endpoints
Method | Endpoint | Actions | Request Payload | Response Payload |
POST | /v2/b2b/reservations | Create a new reservation | Reservation Object | Reservation Object |
GET | /v2/b2b/reservations/{id} | Retrieve an existing reservation by ID | None | Reservation Object |
PUT | /v2/b2b/reservations | Update an existing reservation | Reservation Object | Reservation Object |
DELETE | /v2/b2b/reservations/{id} | Delete a reservation. Use if the user abandons the cart to release capacity. | None | Reservation Object of the Deleted Reservation |
Sample Request Payloads
Create a New Reservation
{ "reservationItems": [{ "eventId": "{{instanceId}}", "quantity": 5 }] }
Update an Existing Reservation
{ "id": 10754, "expirationTimestamp": "2020-01-09T17:07:30-05:00", "reservationItems": [ { "id": 10536, "reservationId": 10754, "eventId": "5d96453460309f26d082bd11", "quantity": 3 } ] }
Sample Responses
A Reservation Object
{ "id": 10754, "expirationTimestamp": "2020-01-09T17:07:30-05:00", "reservationItems": [ { "id": 10536, "reservationId": 10754, "eventId": "5d96453460309f26d082bd11", "quantity": 5 } ] }