OTAPPLead2026
Otapp Flights
One booking engine behind every flight sales channel
WebAPI

Overview
A multi-channel, multi-supplier flight ticketing core. Customer web and mobile, the agent portal, partner APIs and the back office all share one booking engine; a channel changes identity, pricing, supplier routing and payment settings, never the booking logic. It replaces a legacy PHP API.
- 3
- apps: API, portal, booking site
- 86%
- of API commits by me
- 1
- engine for every channel
What I built
- Order state machine: every captured payment ends in a ticket or a visible compensation case
- Supplier plug-in interface: new airline suppliers are added through configuration
- Reusable outbound auth: API key, OAuth2, JWT against JWKS and HMAC signing
- Supplier credentials encrypted at rest and resolved only on the server
Stack
- Java 21
- Spring Boot
- PostgreSQL
- Redis
- Flyway
- Next.js
- MUI
- Playwright
Screens
Building something similar? Let's talk.
yusto@georgeyusto.info