Working with Channel Managers

Channel Managers are third-party systems that connect Distribution Partners to FareHarbor without requiring the partner to connect to FareHarbor’s API directly. We prefer partners to connect to FareHarbor’s API directly, however sometimes they do not have the resources to connect to multiple reservation systems, and go the route of a third-party Channel Manager instead.

Requirements for Channel Managers to work with FareHarbor

To qualify, Channel Managers must go through the same process as any direct API Connection. You can read more about that in the Lifecycle of an API Partner help page.

Like any other API Connection, Channel Managers must receive approval from FareHarbor on where they will distribute our clients’ inventory (i.e. websites, agents, other systems). This is identified in the original API & Data License Agreement the partner must sign before connecting to FareHarbor’s API. FareHarbor will look to avoid any connections we already provide for free or that go against FareHarbor’s interest (i.e. We will not allow a connection to another Booking Reservation System which would be a direct competitor of FareHarbor). For any questions about this topic, please use the correct workflow to ask a question in #strategicpartners-affiliates.

Current Channel Manager Connections

Here is a Smartview of the Channel Managers that are connected to FareHarbor.

Talking Points to cover with Channel Manager Connections

• Third-Party Distribution Partners: Since Channel Managers push our clients products to other parties, it is vital that we know who they are and have approved them. This is clearly stated in the API & Data License Agreement. However, it’s important to cover with the Channel Manager that they will need to update us on any new potential distribution partners in the future. Stress that we reserve the right to not allow access to any distribution partner.
• The importance of value in their connection: FareHarbor provides API access to the world’s top distribution partners for free to our clients. If we choose to work with a Channel Manager it is because they bring additional value to our clients (i.e. distribution partners who are not connected directly to us) that is much greater than their costs.
• Working with the API: We expect Channel Managers to use the API in the same way as our other external API partners, with limited assistance from FareHarbor. They will need to demonstrate control of the API, as our other partners do. During the construction phase, it is important that their developers and engineers develop the API to provide the information in their system that their employees need. This will reduce Support tickets with FareHarbor and ensure that our clients products are distributed more efficiently.

Here are some resources to help you understand Redeam, the best practices for setting them up as an affiliate on a Dashboard, and supporting their API integration.

This should not be used as a guideline for recommending clients to use Redeam. If you are curious about recommending Redeam, please contact @strategic-partnerships in #strategicpartnerships-affiliates first to discuss.

Redeam is a third-party integration provider that helps pass bookings for clients into FareHarbor via our API. They act as a “channel manager,” connecting tour/activity providers to different resellers who don’t currently have their own direct API integrations with FareHarbor. We like to think of Redeam as an integration “middle-man”, helping to reduce the amount of manual bookings for clients, and providing connectivity to resellers that we don’t have our own direct integrations with yet.

Example: The affiliate Groupon generates a lot of bookings for our clients, but we do not have a direct integration with Groupon at this time. Redeam acts as the integration middle-man, connecting bookings made on Groupon through Redeam and then sending the booking via FareHarbor’s API into a client’s FareHarbor Dashboard. More info on Groupon can be found in our API partner glossary here.

*It is important to note that Redeam charges tour/activity providers for their connectivity services.

Visit their website here: https://www.redeam.com.

Redeam is one of FareHarbor’s External API Partners, but they are a very different partner from the typical Online Travel Agencies that we work with. Redeam is not an OTA, and they are not the seller of the product. When working through Redeam, FareHarbor does not have any direct interaction with the actual seller/affiliate. We have a great working relationship, but they only work with a very small number (less than 5) of our clients. We do not need to actively recommend that clients work with Redeam, because 1) we don’t want to advocate that clients pay for connectivity, and 2) we strive to provide connectivity to the same affiliates as they offer.

Reminder: Never put in writing that FareHarbor might recommend against working with any of our API Partners. We are fully supportive of connectivity, and if clients have any questions about Redeam we are glad to assist them.

• They are NOT tagged as the affiliate on the booking
• The affiliate is tagged, but the booking is said to have been created by the Redeam API. See images below.
• Click here to see the connections Redeam manages & the affiliates they can book as.

Affiliate Tag:

Booking History:

• Redeam always has specific affiliate Dashboards for their different API connections, which should only be used by them.
  • For example, while “Groupon” has their own affiliate Dashboard, they must also have a “Groupon (Redeam)” Dashboard.
  • All Redeam-affiliated Dashboards have an added “(R)” or “(Redeam)” in the name and will have “redeam” in the shortname.
    • Example: Groupon (Redeam) and grouponredeam-usd These Dashboards are then given API credentials, so the correct Dashboard is tagged when a booking is made.
  • If Redeam creates a booking using the Groupon (Redeam) API key, then Groupon (Redeam) will be tagged as the affiliate on that booking.
• When adding Redeam as an affiliate, Redeam lets FareHarbor know which affiliate they are connecting via the API and which charter they are passing through bookings for. We then add the correct Redeam affiliate to the charter Dashboard.
• FareHarbor clients have to pay Redeam to have them integrate their affiliate bookings. They must also have an established partnership with the reseller.
• The net rates for Redeam bookings (or the fee clients pay to booking) are not controlled or paid out via FareHarbor.
• All of the “Redeam” affiliate Dashboards must have the Redeam Destination URL plugged in as a webhook, so that Redeam can see updates made to the bookings that they create.
  • Webhook URL: https://fh.redeam.io/bookings
  • Example in a Redeam Affiliate Dashboard: https://fareharbor.com/grouponredeam-usd/dashboard/settings/permissions/users/api/api-keys/