Common Integration Scenario

This article walks through a common end-to-end scenario where a customer browses an event, selects tickets, completes payment, and receives their tickets using the SpurrOpen Partner API. 

• Step 1: Browse Events
  Your system retrieves a list of available events using the GET /events endpoint and displays them to the customer. The customer selects an event they are interested in. 
  
  
• Step 2: View Event Details
  When the customer selects an event, your system retrieves detailed event information using GET /events/{id} and displays the full event details.
   
• Step 3: View Ticket Options
  Your system retrieves available ticket options using GET /events/{id}/tickets and displays ticket types, prices, and availability. 
  
  
• Step 4: View Ticket Details
  If required, your system retrieves ticket-specific details using GET /events/{id}/tickets/{id}, including any purchase requirements or required fields. 
  
  
• Step 5: Preview Order
  Before creating an order, your system calculates the final price using POST /orders/preview and displays the total amount to the customer. 
  
  
• Step 6: Create Order
  Once the customer confirms their purchase, your system creates an order using POST /orders. This temporarily reserves the selected tickets. 
  
  
• Step 7: Collect Payment
  Payment is collected using your own payment system, such as online checkout, card, cash, or mobile payment. 
  
  
• Step 8: Confirm Order
  After payment is successfully collected, your system confirms the order using POST /orders/{id}/confirm. The order is completed and tickets are issued to the customer. 
  The customer receives their tickets via email, and the transaction is complete. 

This scenario is an example. Actual implementations may vary.