Crew Travel API · v1.0.0

Build airline crew travel that runs itself.

RouteSpring turns crew schedules and operational changes into policy-aware hotel and deadhead flight bookings. Start in the sandbox, follow every asynchronous decision, and move to production with the same API surface.

API operations

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
Submit a full roster snapshot
POST /crew/schedules returns a schedule_id and QUEUED status.
2
Poll until processing is terminal
Track QUEUED → PROCESSING → BOOKING → COMPLETED, PARTIAL, or FAILED.
3
Inspect decisions
Read action items, audit events, and booking records tied to the schedule.
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.