Multi-date events (performances)

​

Reading the dates

{
  "performances": [
    {
      "id": "cmv…",
      "name": "Viernes",
      "starts_at": "2026-11-20T20:00:00.000Z",
      "ends_at": "2026-11-21T02:00:00.000Z",
      "status": "ON_SALE",
      "sort_order": 0,
      "total_available": 412,
      "from_price": 60000,
      "sold_out": false
    }
  ]
}

• status is ON_SALE, SOLD_OUT or CANCELLED. Hidden drafts never arrive.
• When there are several dates, each one also carries total_available, from_price and sold_out, so you can draw the selector (“sáb 21 · desde $60.000 · agotada”) from this payload alone.
• ticketAvailability[] stays one row per ticket type × selling stage, summed across the dates, until you ask for one date: GET /api/events/public/{slug}?performance_id=… returns that date’s stock, and each row’s performance_id is set.

​

Selling for a date

{ "ticket_type_id": "…", "selling_stage_id": "…", "quantity": 2, "performance_id": "cmv…" }

​

Recommended UX

1. Render the date selector above the tickets. Preselect nothing (a ?performance= deep link may). Mark sold_out and CANCELLED dates as disabled.
2. On pick, re-fetch the event with ?performance_id= so the ticket list shows that date’s stock, and clear the selection.
3. Show the picked date (not event.start_date) in the header, the checkout summary and the confirmation page.