Appendix
Showcased Attractions
Retrieve curated showcases for featured content:
GET /v2/showcases
Headers: Booking-Session, Coras-Distributor
Returns top_showcase and main_showcase — each containing attractions with banner images, or redirect URLs for filtered search results.
Ticket Delivery Methods
| ID | Description |
|---|---|
| 0 | Pickup at the ticket office |
| 1 | E-ticket sent by email (generated by Coras) |
| 2 | E-ticket sent separately by the event provider |
| 3 | E-ticket sent by email (generated by event provider) |
| 4 | E-ticket sent by email 48 hours before the event |
| 5 | E-ticket sent by email as a download link |
| 6 | E-ticket shared by AXS app |
Transaction status
| Status | Description |
|---|---|
| ADDED | Default status for transactions that are created but not yet processed by Coras. |
| PAID | Status for transactions that have been successfully paid and processed by Coras, and the tickets have been issued. |
| PENDING | Status for transactions that are being processed by Coras, but the final result is not yet known. This includes transactions that are currently being paid, as well as transactions that are currently being processed by the transaction provider. |
| FAILED | Status for transactions that have failed at any point during the payment or processing stages. This includes transactions that failed due to payment issues, as well as transactions that failed during processing by Coras or the transaction provider. |
| SUSPENDED | Status for transactions that have been temporarily suspended. This can happen when there are issues with the payment provider. |
| REFUNDED | Status for transactions that have been successfully refunded. |
| PARTIAL_REFUNDED | Status for transactions that have been partially refunded. This means that some tickets have been refunded, but not all of them. |
| CANCELLED | Status for transactions that have been cancelled. This means that the transaction was successfully paid, but the customer or Coras decided to cancel the transaction. |
| PARTIALLY_CANCELLED | Status for transactions that have been partially cancelled. This means that some tickets have been cancelled, but not all of them. This can happen when a customer cancels part of their order, or when Coras cancels part of the order due to issues with the transaction provider or the tickets. |
| PARTIALLY_CONFIRMED | Status for transactions that have been partially confirmed. This means that some tickets have been confirmed, but not all of them. This can happen when a order contains tickets from multiple providers and some of them are confirmed while others are not. |
Quick Reference: Endpoint Summary
| Action | Method | Endpoint | Notes |
|---|---|---|---|
| Create booking session | POST | /v2/booking-session | |
| Update booking session | PUT | /v2/booking-session | |
| Get common data | GET | /v2/common | |
| Get attraction types | GET | /v2/attraction-types | |
| Search attractions | GET | /v2/attractions | |
| Get attraction (any type) | GET | /v2/attractions/{id} | Unified — replaces type-specific endpoints |
| Get showcased attractions | GET | /v2/showcases | |
| Get theater instance | GET | /v2/theater-events/{id}/instances/{instance_id} | Not deprecated |
| Get seats | GET | /v2/theater-events/{id}/instances/{instance_id}/seats | Not deprecated |
| Check availability | POST | /v2/availability/check | Unified — replaces /tours/availability |
| Reserve tickets | POST | /v2/reservations | Unified — replaces type-specific endpoints |
| Get reservation summary | GET | /v2/reservations | |
| Check reservation status | GET | /v2/reservations/check | |
| Confirm (async) | PUT | /v2/reservations | Returns client_secret for Stripe.js |
| Confirm (sync) | POST | /v2/reservations/confirm | Immediate confirmation, no webhook |
| Update reservation | PATCH | /v2/reservations/{id} | Update tickets/attendees |
| Add to basket | PUT | /v2/reservations/{id} | |
| Cancel single reservation | DELETE | /v2/reservations/{id} | |
| Cancel all reservations | DELETE | /v2/reservations | |
| Add attendees | POST | /v2/attendees | |
| Update attendees | PUT | /v2/attendees | |
| Get transactions | GET | /v2/users/{user_id}/transactions | |
| Phone number verification | POST | /v2/phone-number-verification |
Deprecated Endpoints
The following endpoints still work but are deprecated. Use the unified replacements for all new integrations.
| Deprecated Endpoint | Replacement | Notes |
|---|---|---|
GET /v2/theater-events/{id} | GET /v2/attractions/{id} | Response includes attraction_type: "THEATER" |
GET /v2/tours/{id} | GET /v2/attractions/{id} | Response includes attraction_type: "TOUR" |
POST /v2/theater-events/reservations | POST /v2/reservations | Unified endpoint handles both types |
POST /v2/tours/reservations | POST /v2/reservations | Unified endpoint handles both types |
POST /v2/tours/availability | POST /v2/availability/check | Same request/response format |
GET /v2/transactions/{customer_id} | GET /v2/users/{customer_id}/transactions | URL restructured |
GET /v2/cities | GET /v2/common | Cities included in common data |
Migration Notes
- No breaking changes — deprecated endpoints use the same backend classes and return the same response format as their replacements.
- Unified endpoints accept both theater and tour data. The
attraction_typefield in responses distinguishes the type. - Theater sub-routes (
/v2/theater-events/{id}/instances/{instance_id}and.../seats) are not deprecated — they have no unified equivalent and remain the current API surface for instance/seat data.