Integration Overview

About Redeam

The Redeam Booking API provides a flexible solution for Resellers and Online Travel Agencies (OTAs) to connect with tour and activity Suppliers, using real-time pricing, availability, managing holds and bookings and more. We are happy to have an informal conversation about what and how the Redeam Booking API can work for your company, please get in touch sales@redeam.com

Once an agreement with Redeam is in place and you are ready for your Redeam Reseller API integration, please refer to the detailed process for connecting to the Redeam Platform. It consists of five stages:

Phase 1 - Registration

The Redeam team will contact you once the questionnaire details have been reviewed and start the integration process with one or more technical design and review meetings. During these meetings, the Redeam team works with you to identify any unique system requirements between your and the Supplier systems.

We are committed to your successful integration and provide support during your development against our APIs, this can be email-based support (Redeam team will share an email address in the Welcome email) or private Shared Slack Channel for near real time support (Please note that this requires your company to have a paid Slack account)

1. Reseller complete the Connection Questionnaire which Redeam send in the Welcome email
2. Redeam provide sandbox credentials to Booking API in the Welcome email
3. Reseller determines their preferred method of communication: Slack or email
4. Redeam review the Connection Questionnaire details and start required integration documentation

Phase 2 - Kick-off, Team introductions and Development

The Redeam team set up a kick off call after sending out the integration documentation to introduce themselves and make sure the Reseller team know their contacts at Redeam. They also run through the Connection Questionnaire, the connection process and any questions from the Reseller team.

1. Technical kick-off call between Reseller and Redeam
2. Reseller use the Booking API spec to develop to Redeam
3. Redeam provide technical support via preferred method of communication
4. Reseller confirm their development is complete

Phase 3 - Certification

Once your development is complete, a Redeam engineer carries out 2-way certification by running a suite of test scripts. Once this is passed and the transactions flow correctly, 3-way testing between all 3 parties (you, Supplier and Redeam) can be set up in sandbox and a certification call scheduled. We prefer online certification for speed and efficiency of potential hold ups in the transaction flow. The certification is successful once all 3 parties approve of the transaction flow.

1. Redeam Account Manager schedules certification with CS Engineering team
2. Certification covers visibility of suppliers, products and rates, ability to post bookings and cancellations
3. Reseller provide copy of the voucher they issue to their guests, Supplier signs off on the voucher data
4. 3-way test between Reseller - Redeam - Supplier (first time only)

Phase 4 - Production Pilot

After a successful 3-way certification, the pilot can go ahead, Redeam recommend to avoid Thursdays and Fridays. The Operator and Reseller channels are bound which means both parties can select the new partner connection.

1. Redeam configure Reseller for Production and provide production credentials for Redeam Booking API
2. Reseller coordinate with contracted Supplier to get ready for production pilot
3. Redeam make Supplier / Ticketing System channel visible to Reseller
4. Redeam confirm to Supplier / Ticketing System that production is setup
5. Reseller confirm once Redeam Booking API is ready for production sales and make a test booking
6. Monitor connection for first guest bookings and confirm Supplier receives all data required from Reseller

Phase 5 - Live

The Reseller booking channel is live and producing. Any requests from Resellers to add additional connections to contracted Suppliers should be directed to Redeam Customer Success on support@redeam.com.

Security & Performance

At Redeam we are constantly checking and updating our platform to keep data and transactions secure which is reflected in our processes and transaction APIs.

• All customer integrations are protected with API keys and secrets
• All communications are done over secure TLS 1.3
• All PII information is encrypted throughout Redeam, both on the wire and at rest with strict RBAC mechanisms

To avoid production environment performance issues, we monitor timeouts and hold times for of connections and make recommendations for improvement. If we come across anything that would jeopardize security or performance, we will notify our partners. Depending on the issue, we send out notifications to give our partners time to rectify it, however we do reserve the right to disable a partner's interface if no action is taken depending on severity.