Crew Travel API — Interactive Walkthrough

Step 0 — get your API credentials. Open the Routespring dashboard → Settings → Integrations → REST API, create an API token, and copy the client_id / client_secret it gives you. Paste them below.

1. The link drops you straight on the Developer / REST API settings page.
2. Follow the on-screen steps to create a token (it issues a client_id + client_secret).
3. Paste both here, add a traveller email (must have a date of birth on their profile), and press Start.

Before you run it — what has to be switched on already. The lifecycle below always completes and always returns 200/202. Whether it actually books depends on configuration that is approved outside this page, so on a company where that has not been done you will see the work land as a review item rather than a booking. That is the API behaving correctly, not an error.

1. An approved hotel contract at the layover station. A hotel only prices a night when its rates are attached to a contract that is switched on for automated booking. Configuring the hotel — which step 3 does — is not enough on its own: without the contract the layover comes back NEEDS_REVIEW saying the station has no hotel config, even though step 3 just set one. Switching a contract on is a reviewed action, so it has to exist and be approved before the schedule is submitted.
2. Deadhead auto-booking, if you want the flight booked for you. With it off — the default — every NEW_DEADHEAD is returned as PENDING_REVIEW with a flight_options_url, and you pick and commit the flight yourself. That is what steps 6–8 below do, so the walkthrough works either way.

You can set the contract up yourself through this API: POST /crew/config/hotels/{hotel_config_id}/contracts, then PUT …/contracts/{contract_id}/rates covering the contract's full date range, then POST …/hotels/{hotel_config_id}/change-requests with intent: ENABLE. Approving that request is an agent action and is deliberately not on this API — so on a company that has never been set up, a first run stops at the review step by design rather than booking the hotel. Ask your Routespring contact to approve it, and to switch on deadhead auto-booking if you want that too. The full list is in the API reference.