Implementation guides
Build the workflows behind airline crew travel.
Each guide starts with the operational problem, shows where the API fits, and provides a contract-accurate implementation path. Use them with operations and finance teams before writing production code.
Updated Current v1 guides
Choose the outcome
OCC, Crew Services, engineering
Automated IROPS recovery
Situation: A cancellation or schedule break creates an urgent hotel or deadhead requirement.
Outcome: Your operations system sends one correlated event, Routespring books against policy, and people handle only holds or failures.
Crew Scheduling, IT, travel operations
Automated scheduled bookings
Situation: A new roster or pairing change creates hotel nights and deadhead positioning work.
Outcome: The roster becomes the operating input. Routespring derives booking actions and preserves a traceable result for every change.
Finance, procurement, data teams
Reconciliation-ready booking ledger
Situation: Finance needs to match supplier charges to what operations requested and what the supplier confirmed.
Outcome: Booking identifiers, operational anchors, rate evidence, status history, and exports feed a controlled matching process.
Use the guides as an operating design
1. Name the source event
Define which roster publish, OCC decision, or finance record starts the workflow.
2. Preserve airline identifiers
Carry employee, pairing, duty, flight, schedule, and IROP references across system boundaries.
3. Decide the human boundary
Define which policy exceptions, price limits, failures, and supplier states require review.
4. Close the record
Store the booking outcome and export the evidence needed by operations, support, procurement, and finance.