Connection Process
Fundamentals of connecting to our system
The process for connecting to the Redeam Platform consists of five stages presented below.
- Phase 1 – Registration
- Phase 2 - Kick off - Team introductions and Development
- Phase 3 - Certification
- Phase 4 - Production Pilot
- Phase 5 – Live
Phase 1 - Registration
- Complete connection Questionnaire
- Sign connectivity Agreement with BD
Phase 2 Kick off - Team introductions and Development
- Technical kick off call between Operator/Ticketing System and Redeam Tech
- Redeam will provide sandbox credentials to Operator/Ticketing System
- Operator/Ticketing System will use Channel API to push all of their DATA into Redeam
- Operator/Ticketing System will implement a set of endpoints according to the Partner API specifications
Phase 3 Certification
- Operator/Ticketing System will provide Redeam with those endpoints in the form of Host name/Domain name , and provide an API Key and API Secret
- Redeam CS Engineers will validate Operator/Ticketing System data objects that they pushed in
- Redeam CS Engineers will validate the Partner API Implementation to make sure that before we move to Production, that the bookings are flowing through the full circuit correctly.
- Operator/Ticketing System will test via Sandbox
- Operator/Ticketing System will sign off on their Sandbox Testing and Request Production Credentials
- Redeam will provide Production Credentials
Phase 4 Production Pilot
- Redeam Account Manager will schedule a Pre Launch call to discuss the 3rd Party/Reseller(S) that they want to connect live with
- Operator/Ticketing System will push all of their inventory into Redeam using the Channel API in Production
- Operator/Ticketing System will implement a set of endpoints according to the Partner API specifications (same process as Sandbox testing)
- Operator/Ticketing System will provide Redeam with the Production endpoints, API Key and API Secret
- Redeam CS Engineers will validate Operator/Ticketing System data objects that they pushed in
- Redeam will make Operator/Ticketing System visible to 3rd party/Reseller
- Redeam will confirm to Operator/Ticketing System that production is setup
- 3rd Party/Reseller will execute test transactions in Production
- 3rd Party/Reseller will confirm when they have begin business sales over API
- Guest initiates booking
- Redeam receives booking from 3rd Party/Reseller
- Redeam pushes reservations/bookings from Reseller into Operator/Ticketing System.
Phase 5 Live
Once a booking channel is certified and the pilot successfully completed, the booking channel name will be logged with the Redeam sales & support teams as being production enabled. Requests for new production connections can be to Redeam Customer Success by the Operator
Redeam Sales will ensure that the Operator requesting connectivity is appropriately aware of the connection and ensure that the Redeam Customer Success is made aware of the pending set up and will manage Operator go live expectations.
Was this page helpful?