Architecture Overview
Coras acts as an aggregator between your application (the distributor) and multiple ticketing providers (Spektrix, Secutix, TourCMS, etc.). As a distributor, you interact only with the Coras API — you never communicate directly with providers.
┌──────────────┐ ┌──────────────┐ ┌──────────────────┐
│ Your App │ ──────▶ │ Coras API │ ──────▶ │ Ticket Providers│
│ (Distributor)│ ◀────── │ (Exchange) │ ◀────── │ (Spektrix, etc.)│
└──────────────┘ └──────────────┘ └──────────────────┘
│
▼
┌──────────────┐
│ Stripe │
│ (Payments) │
└──────────────┘
Key concepts:
| Concept | Description |
|---|---|
| Attraction | A bookable event — either a theater show or a tour/activity |
| Instance | A specific date/time occurrence of an attraction |
| Price Band | A seating section or tier with its own pricing (theater) |
| Price Type | A category of ticket (e.g., Adult, Child, Senior) |
| Booking Session | A temporary session (20 min TTL) that holds your reservations |
| Reservation | A hold on tickets within a booking session |
| Transaction | A confirmed and paid booking for one or more reservations |
Attraction types:
| ID | Type | Description |
|---|---|---|
| 1 | THEATER | Theater shows, concerts, sports matches, events with assigned seating |
| 2 | TOUR | Tours, activities, and sightseeing experiences |