# en-tri

en-tri is the booking layer for small sports events. The organiser is the hero: en-tri helps them create a session, sell spots, publish it to many channels, and keep one roster.

Primary docs for AI agents:

- Integration API guide: https://en-tri.com/docs/INTEGRATION_API.md
- OpenAPI specification: https://en-tri.com/api/openapi.json
- Project source of truth: this repository's `PROJECT_BRIEF.md`

Core rule:

If a field affects whether someone can book, pay, attend, or take a spot, en-tri owns it. If a field affects discovery, SEO, branding, sport-specific presentation, or marketplace ranking, the channel owns it.

Recommended partner architecture:

Your site sells the event. en-tri sells the spot.

Current public API entry points:

- `GET /api/channels/{channelSlug}/events`
- `GET /api/channels/{channelSlug}/events?organiser={organiserSlug}`
- `GET /api/channels/{channelSlug}/events/{organiserSlug}/{eventSlug}/bookings`
- `POST /api/channels/{channelSlug}/bookings`
- `POST /api/payment-intent/{organiserSlug}/{eventSlug}`
- `POST /api/payment-confirm/{organiserSlug}/{eventSlug}`
- `POST /api/booking-followup/{organiserSlug}/{eventSlug}`

Use `signupSource=api` and `signupChannel={channelSlug}` for native partner integrations.