API roadmap
The current API automates schedules, actions, policy, bookings, retries, audits, hotel inventory, and exports. These planned families cover the next system boundaries airlines have to connect.
Updated Planned capabilities, not part of v1
Operations and platform teams
Receive schedule, action, booking, retry, and IROP state changes without polling each resource.
Design direction: Signed event delivery, replay protection, event IDs, delivery history, and subscription controls.
Finance and procurement
Connect supplier documents to booking evidence, classify variances, and track approval or dispute state.
Design direction: Document ingestion, line items, matching results, exception reasons, evidence, and finance handoff.
Crew Services and OCC
Coordinate airport-to-hotel transport in the same scheduled and IROPS workflow as lodging.
Design direction: Transport requirements, supplier selection, reservation state, pickup details, and event correlation.
Finance and traveler operations
Issue controlled value for crew needs and track payment or supplier settlement through completion.
Design direction: Allowance rules, payment instruments, authorized spend, transaction state, and settlement evidence.
Procurement and hotel operations
Manage more of the commercial hotel record and measure whether execution follows contracted terms.
Design direction: Contract periods, inclusions, blackout rules, allotments, amendments, and supplier performance.
HRIS, crew systems, and platform teams
Keep bookable crew identity and eligibility synchronized without relying on email lookup alone.
Design direction: Profile lifecycle, employee and base anchors, bookability, preferences, and policy assignment.
Submit complete roster windows and inspect the hotel or deadhead work derived from each change.
Manage company policy, preferred hotels, flight preferences, and flight rules.
Search, request, modify, cancel, refresh, and retry booking work with traceable state.
Create urgent hotel or flight requirements with airline correlation IDs and safe idempotency.
Read data-quality findings and export schedule actions for airline analytics.
Search available hotel inventory exposed by the current service.
The useful design input is a real operating boundary: the source system, the decision that should be automated, the identifiers that must survive, the exception owner, and the evidence the next team needs. Bring that workflow to the Routespring team before locking a future-facing architecture.
Discuss an API workflow