01 / USE CASE
Define the route
Identify the partners, transfer airport, separate tickets, and baggage acceptance and transfer requirements. First, establish who is responsible for each stage of the process.
RuBI / FOR TECHNICAL & OPERATIONS TEAMS
More than a button.
An end-to-end connection.
Technical integration works alongside procedures agreed by airlines, the airport and ground handlers. The outline below provides a starting point for our first discussion.
02 / SYSTEMS
Identify the integration points
Review the available interfaces for reservations, passenger and baggage check-in, and ground handling. APIs, messages and events are agreed with the system owners.
03 / DOCUMENTATION
Link the baggage journey
Define the identifiers, digital voucher content, baggage tagging rules and handling instructions. The document does not replace airport authorisations or procedures.
04 / EXCEPTIONS
Agree disruption procedures
Document the actions required for flight delays, missing status updates, itinerary changes and baggage issues. Assign responsibilities and agree an escalation procedure.
05 / TESTING
Test the complete process
Test the technical data exchange, validate the documents and verify the operational handover. Define measurable acceptance criteria for the pilot route.
06 / LAUNCH
Launch in stages
Once the results are approved, agree the routes, service scope and support arrangements. Expand only to validated combinations of partners and processes.
This is a framework for discussing integration, not published documentation for a live API. Service endpoints, access credentials, message formats and each party’s obligations are provided and approved separately.
What to prepare for the first meeting
Partners: airlines, airport, ground handler Route: departure, transfer and destination airports Systems: reservations, DCS, BHS / ground handling Data: flight, baggage and document identifiers Procedures: acceptance, handover, exceptions, completion Contacts: IT and operations leads Criteria: acceptance and launch requirements
Discuss data requirements through an agreed secure channel. Do not submit passport or payment details through the website form.