Channel API Opt Out Processes

If the client still wants to disconnect, there are a few places where the change has to be reflected:

FH Dashboard / Settings / Integrations

• Change SKU entry to “Google – Opted Out”. The OTA type can remain as is in the channel company settings.
• Go to Affiliates and remove the Affiliate – API permissions from the Google affiliate.

Airtable

• Locate the record in the Master view and set Status to Opted Out.
• Add any relevant comments to Notes (like a URL to a ticket with opt-out request).

Close

• Locate their lead and edit the “Connectivity-Live” custom field, uncheck Google.
• Add the “API – Google Opt-Out” custom field and select “yes”. Make sure to save the changes.

Zendesk

If there’s a ticket related to the TTD opt-out or the client needs a follow-up:

• Update the ticket and follow up with the client if needed. Please mention to the client that it might take up to several hours until the changes sync to their Google Business page.
• Slack the AM in #connectivity using the “API opt-out” workflow.

When a client requests to opt-out of their Booking.com integration, forward the opt-out request to Channel Support and there are a few places where the change has to be reflected for Connectivity.

Forward the opt-out request to Channel Support

• Channel Support will submit a form to Strategic Partnerships (depending on whether it involves just FHDN API or referral links).

• Strategic Partnerships will:

  • Remove the affiliate from the dash.
  • Update the lead in Close by removing the FHDN contracts.

⚠️ Important ⚠️: Connectivity should never remove or update the FHDN API affiliate.

FH Dashboard

• Change SKU entry to “Booking.com FHDN – Opted Out”. The OTA type can remain as is in the channel company settings.
• Unselect the “Visible to Booking.com API” checkbox on the in the channel item settings.

Airtable

• Locate the record in the Master view of the Queue to Connect tab and update the status to “Disabled.” Issue status – “Opted out”.
• Add any relevant info to Reason and Notes columns (like a URL to a Zendesk ticket with the opt-out request).

There are a few places where the change has to be reflected:

API Partner Dashboard

• If we still have access to their Viator account, log in and remove the connections on each product.
• Remove FH as the reservation system in their Viator supplier account. Click on Account –> Connectivity –> Connectivity Details –> Edit –> Remove Connection.
  • Mark the reason for disconnection as “unhappy with connection”.
• For Expedia and GYG the client can disconnect in their supplier accounts or email the OTA to disable those.

• For Airbnb, the client can follow the below steps:

  • Log in to the Airbnb account currently connected to FareHarbor.
  • Click your profile photo in the top right corner and select Account from the dropdown menu.
  • Navigate to Privacy & sharing.
  • Open the Services tab.
  • Locate FareHarbor and click Remove access.

FH Dashboard / Settings / Integrations

• Change SKU to include “Opted Out” (Ex: Viator – Opted out). The OTA type can remain as is in the channel company settings.
• Remove Viator API ID and Key in the channel company settings.
• Remove Airbnb Host ID and Activity ID in the channel item settings.
• Note: GYG, Expedia and Website Travel don’t have an equivalent in this case.
• Go to Affiliates and remove the Affiliate – API permissions from the appropriate affiliate.

Airtable

• Locate the record in the Master view of the Queue to Connect tab and update the status to “Disabled.” Issue status – “Opted out”.
• Add any relevant info to Reason and Notes columns (like a URL to a Zendesk ticket with the opt-out request).

Close

• Locate their record and edit the “Connectivity Live” custom field, uncheck the appropriate API. Make sure to save the changes.

Zendesk

If there’s ticket related to the API opt-out or if the client needs a follow-up:

• Update the ticket and follow up with the client if needed. Please mention to the client that it might take up to several hours until the changes sync to Viator but the bookings will be blocked immediately on FH side.
• Slack their AM in #connectivity using the “API opt-out” workflow.

Optional: For WebsiteTravel only and only if you have a login for the client’s WT dashboard:

• Go to My Details, E-Bookings Setup section and if you see “Configure Operator API Connection”.
• Click it and remove Generic/WebsiteTravel entry and save changes. This removes FH API key from this particular client’s WT dash.

API Partner Dashboard

• If we still have access to their Viator account, log in and remove the connections.
• For Viator, remove FH as the reservation system in their supplier account. Click on Account –> Connectivity –> Connectivity Details –> Edit –> Remove Connection. Mark the reason for disconnection as “unhappy with connection”.

FH Dashboard / Settings / Integrations

• Go to Affiliates and remove the Affiliate – API permissions from any API affiliates.
• Remove Supplier ID & API key from Viator channel mapping.

Airtable

• For Channel APIs, locate the record(s) under the Master view and set status to “Disabled.” Issue status – “Offboarded”.

Close

• Locate their lead and remove the “Connectivity-Live” custom field. Make sure to save the changes.