Routespring Logo
Request Demo

Crew Travel API · v1.0.0

Connect airline operations to travel execution.

Routespring turns crew schedules and disruption decisions into policy-aware hotel and deadhead bookings. Operations teams get fewer manual queues, finance gets a traceable record, and developers get one API to connect the workflow.

Updated Current v1 documentation

What this API covers

Operating input
Complete crew schedule snapshots and urgent IROPS travel requirements.
Automated work
Policy-aware hotel and deadhead actions, bookings, changes, cancellations, and safe retries.
Human boundary
Policy holds, price exceptions, unavailable inventory, and failed supplier calls remain visible for review.
Source of truth
The v1 API reference and downloadable OpenAPI contract define what is available today.

What changes for the airline

The API sits between the systems that know what the crew needs and the suppliers that fulfill it. It carries the operational identifiers, applies configured policy, executes eligible bookings, and makes exceptions visible.

Operations gets an exception queue

Routine schedule changes can become bookings automatically. OCC and Crew Services stay focused on holds, failures, and policy decisions.

IT keeps the workflow controlled

One authenticated integration carries airline identifiers, policy, booking state, retries, and an audit trail across the process.

Finance gets cleaner evidence

Booking anchors, supplier confirmations, contracted rates, booked rates, and exports create a stronger handoff into reconciliation.

Start with a real workflow

Day of operations

Automate IROPS recovery

Turn an OCC disruption signal into urgent hotel or deadhead action, preserve human approval where needed, and report the event by one IROP reference.

Follow the tutorial

Scheduled operations

Automate crew bookings

Submit a roster snapshot, let Routespring derive hotel and deadhead work, then route only exceptions back to the operating team.

Follow the tutorial

Finance handoff

Build a reconciliation-ready ledger

Export decisions and booking records with the identifiers and rate evidence finance needs to match operational travel to supplier charges.

Follow the tutorial

29

API operations

79

typed schemas

OpenAPI 3.1

machine-readable contract

Make your first request

RouteSpring uses OAuth2 client credentials. Exchange the credentials issued during onboarding for a short-lived bearer token, then call the sandbox gateway.

Terminal
export AUTH_BASE="https://oauth-sandbox.routespring.com"
export BASE="https://sandbox.routespring.com/api/v1"

# Exchange your client credentials for a short-lived access token.
curl -sS -X POST "$AUTH_BASE/oauth/token?grant_type=client_credentials" \
  -u "CLIENT_ID:CLIENT_SECRET"

# Use the returned access_token on every API request.
curl -sS "$BASE/crew/schedules?limit=20" \
  -H "Authorization: Bearer $ACCESS_TOKEN"
Follow the quickstart Explore all endpoints

One API, the complete crew workflow

Automate crew hotels

Submit complete roster snapshots and let RouteSpring derive, book, modify, and cancel layover stays.

Book deadhead flights

Search flight options, commit airline-selected itineraries, and track supplier state through ticketing.

Recover from IROPs

Inject urgent action items outside the roster cycle and use retry controls for failed supplier calls.

Control policy

Configure hotels, contract rates, airline preferences, cabin, and auto-book price ceilings.

The schedule lifecycle

  1. 1

    Submit a full roster snapshot

    POST /crew/schedules returns a schedule_id and QUEUED status.

  2. 2

    Poll while processing is active

    Continue while poll_recommended is true; stop when the API returns false.

  3. 3

    Inspect decisions

    Read action items, audit events, and booking records tied to the schedule.

  4. 4

    Operate exceptions

    Review policy holds, refresh supplier status, or retry failed bookings.

Asynchronous by design

Never infer completion from an empty action-item list.

Idempotent configuration

PUT replaces the active config and creates a retrievable version.

Opaque identifiers

Store flight option and pagination tokens exactly as returned.

What comes next

The current v1 contract covers schedules, action items, configuration, bookings, retries, audits, hotel inventory, and exports. The roadmap describes planned API families for event delivery, invoice and folio reconciliation, ground transport, payments, supplier contracts, and crew profiles. Planned capabilities are not part of the current v1 contract and may change before release.

Review the API roadmap