01

Confirm access and permission

Ask which API capabilities are available to the operator’s account, how access is authorised and whether a sandbox exists. Public product marketing is not confirmation that a specific endpoint or commercial permission is available.

02

Name the source of truth

Identify where fares, availability, booking IDs and status originate. Record required fields, accepted formats and how updates are represented. Distinguish a received request from a committed booking.

03

Plan for failure

Agree timeouts, retry limits, duplicate protection and a visible manual fallback. Decide how staff will learn that a request needs attention without exposing unnecessary passenger information.

04

Test the complete workflow

Check valid requests, missing fields, rejected bookings and repeated updates. Review access controls and logging. Confirm production behaviour before publishing a claim that the connection is live.

YOUR WORKING CHECKLIST

Take it into your next review.

0 of 6 checked · kept in this page only

MAKE THE NEXT CONNECTION

Put the questions
to work for your fleet.

Booking system integration