Frais API et processus de facturation

Comment puis-je activer la connectivité API ?

• USA et Porto Rico : Cochez la case “Autoriser les réservations API à être soumises à des frais API” dans Paramètres avancés de l’entreprise > Réservations > Réservations API avant votre date d’entrée en vigueur. Assurez-vous également qu’une méthode de facturation est présente dans Paramètres > Banque et paiements > Facturation.
• Tous les autres lieux : Ajoutez simplement une méthode de facturation à votre tableau de bord dans Paramètres > Banque et paiements > Facturation.

Où se trouve la case à cocher “Autoriser les réservations API à être soumises à des frais API” ?

Vous trouverez cette case à cocher dans votre tableau de bord sous Paramètres > Paramètres avancés de l’entreprise > Réservations > Réservations API. Veuillez l’activer avant votre date d’entrée en vigueur pour continuer à recevoir automatiquement les réservations API.

J’ai des difficultés à ajouter une méthode de facturation. Que dois-je faire ?

Veuillez essayer ce qui suit :

• Déconnectez-vous et reconnectez-vous.
• Essayez de vous connecter sur un autre navigateur ou en mode navigation privée.
• Utilisateur externe : Si vous êtes un utilisateur externe avec plusieurs tableaux de bord, connectez-vous à chacun séparément pour ajouter la méthode de facturation.
• Permissions insuffisantes : Vérifiez que votre utilisateur de tableau de bord dispose des autorisations pour gérer les comptes bancaires sous Nom du groupe > Configuration > Gérer les comptes bancaires. Un employé de FareHarbor peut vérifier cela pour vous.
• Informations de contact incomplètes : Assurez-vous qu’une adresse e-mail est présente dans les Informations de contact du tableau de bord (pas seulement dans la section de facturation).
• Problèmes de carte de crédit : Si vous utilisez une carte de crédit, contactez l’émetteur de votre carte, car il peut y avoir des restrictions empêchant son ajout.

Si aucune de ces solutions ne fonctionne, veuillez soumettre un ticket de support et inclure :

• Le nom abrégé de votre entreprise, l’utilisateur du tableau de bord et le niveau d’autorisation.
• Une capture d’écran de l’onglet console/réseau de votre navigateur (suivez ces étapes).

Quel est le cycle comptable des frais API ?

Votre facture API sera disponible dans votre tableau de bord au plus tard le 1er jour de chaque mois (précédemment le 3e du mois), couvrant les réservations API effectuées (date de disponibilité) le mois précédent. Les frais seront débités le 6 du mois, avec une nouvelle tentative le 13 si le débit initial échoue.

• Exemple : Pour les réservations API effectuées en janvier, votre facture sera disponible au plus tard le 1er février et débitée le 6 février.
• Important : Assurez-vous que vos réservations sont correctement tarifées au plus tard le dernier jour du mois. Les réservations annulées ou modifiées après le dernier jour du mois seront toujours facturées pour ce mois, et aucun remboursement ne sera accordé (par exemple, si vous annulez une réservation de janvier le 4 février, elle figurera toujours sur votre facture de janvier).

Serais-je facturé pour les réservations annulées ou celles qui n’ont pas été effectuées via l’API ?

Seules les réservations actives et non annulées seront facturées.

Serai-je facturé pour les réservations contestées ?

Étant donné que les paiements des réservations ont lieu en dehors de FareHarbor, notre système ne fait pas de distinction entre les réservations payées et contestées. Par conséquent, bien que rares, les réservations API contestées seront facturées.

Quel est le seuil minimum de facturation ?

Les factures sont soumises à un seuil minimum basé sur les limitations de Stripe indiquées dans leur page d’aide sur les paiements. Si votre facture est inférieure à ce seuil, le montant sera ajouté au débit du mois suivant jusqu’à ce que le minimum soit atteint, puis débité.

Comment les frais API sont-ils calculés ?

Nous calculons les frais en pourcentage du “Total payé à l’affilié” pour les réservations connectées à l’API. Ce total inclut les taxes, conformément aux normes de l’industrie. Les réservations créées manuellement par un utilisateur du tableau de bord ne seront pas facturées, même pour les affiliés dont les réservations proviennent généralement de l’API.

Comment savoir quels affiliés seront facturés des frais API ?

Les affiliés connectés via API ont généralement “- API” dans leur nom. Cependant, notre outil de facturation est conçu pour exclure les réservations manuelles des frais, même pour ces affiliés.

Où puis-je trouver ma facture de frais API ?

Votre facture de frais API sera disponible dans votre tableau de bord sous Rapports > Comptabilité > Documents de traitement des paiements dès le 1er jour calendaire de chaque mois. Les factures sont accessibles uniquement via le tableau de bord et ne seront pas envoyées par e-mail.

Comment puis-je télécharger ma facture de frais API ?

1. Naviguez vers Rapports > Comptabilité > Documents de traitement des paiements.
2. Cliquez sur l’ID du document de la facture.
3. Faites un clic droit sur le document et sélectionnez Imprimer.
4. Choisissez Enregistrer au format PDF comme destination.
5. Cliquez sur Enregistrer.

Comment exécuter un rapport sur les réservations API ?

Pour consulter les affiliés API et les réservations inclus dans les frais API, accédez au rapport Rapprochement des frais API sous Rapports > Comptabilité > Rapprochement des frais API.

Les détails de ma facture de frais API peuvent-ils être modifiés ?

Les détails de la facture sont tirés de Stripe. Pour les mettre à jour, vous devez revérifier votre compte Stripe et ajuster les détails via Stripe si nécessaire. Les détails mis à jour apparaîtront sur les futures factures.

Comment la taxe est-elle gérée sur la facture des frais API ?

Les taxes à la consommation telles que la taxe de vente, la TVA et la TPS ne sont généralement pas incluses sur les factures de frais API, car il s’agit de transactions interentreprises (B2B). Dans la plupart des cas, les entreprises sont responsables de l’auto-évaluation et du versement de toute taxe applicable via leurs propres déclarations fiscales locales. Cependant, si votre entreprise n’est pas immatriculée à la TVA, la transaction peut être traitée comme une transaction grand public (B2C), auquel cas la taxe peut être appliquée au point de vente et directement reflétée sur la facture.

EMEA – Pays-Bas

Si votre entreprise est située aux Pays-Bas, la TVA néerlandaise sera incluse dans votre facture de frais API.

EMEA – Hors des Pays-Bas

Si votre entreprise est située dans l’UE mais en dehors des Pays-Bas, FareHarbor applique les règles de l’autoliquidation de la TVA de l’UE : * Si un numéro d’identification TVA valide a été fourni lors de votre vérification Stripe, la TVA ne sera pas incluse sur votre facture. * Si un numéro d’identification TVA valide n’a pas été fourni lors de votre vérification Stripe, la TVA sera incluse sur votre facture conformément aux règles de TVA néerlandaises.

Amérique du Nord

En raison de la nature de nos services et des réglementations fiscales locales, FareHarbor n’applique aucune taxe (de vente) aux factures de frais API émises aux fournisseurs aux États-Unis.

APAC – TPS Voici l’approche de FareHarbor en matière de TPS en Australie et en Nouvelle-Zélande, conformément aux règles locales pour les fournisseurs non-résidents de services numériques :

• Si vous avez fourni un numéro d’enregistrement GST valide lors de votre vérification Stripe, FareHarbor n’inclut pas la GST sur vos factures de frais API ou de frais de traitement. Vous êtes responsable de l’auto-comptabilité de la GST conformément à vos lois fiscales locales.
• Si vous n’avez pas fourni de numéro d’enregistrement GST valide, FareHarbor est tenu d’inclure la GST sur votre facture conformément à la loi fiscale applicable.

Le calcul des frais API et le traitement de la GST sont des processus distincts et distincts, régis par des principes différents :

• Calcul des frais API : FareHarbor calcule les frais API en fonction de la valeur totale de la transaction (VTT) qui nous est soumise. La VTT reflète le montant total facturé au consommateur. Cela assure la cohérence sur les marchés et s’aligne sur l’accord commercial de FareHarbor avec le fournisseur (généralement un pourcentage fixe de la VTT).

• Traitement de la TPS : La TPS est déterminée séparément du calcul des frais et est régie par la loi fiscale locale. En tant que fournisseur non-résident, FareHarbor n’est pas tenu de facturer la TPS sur les factures lorsque le fournisseur a soumis un numéro d’enregistrement TPS valide.

  • Bien que la TPS ne soit pas ajoutée à la facture dans ces cas, FareHarbor tient toujours compte de la TPS applicable dans nos rapports fiscaux internes et nos obligations de conformité via le mécanisme d’autoliquidation.

Cette structure reflète l’approche utilisée pour les frais de réservation : les valeurs de transaction peuvent inclure la TPS, mais les factures émises par FareHarbor aux fournisseurs peuvent ne pas l’inclure, selon le statut de votre entreprise et de votre immatriculation fiscale. Cette distinction garantit : * Un calcul des frais transparent et cohérent, * La conformité aux lois fiscales régionales, et * Un modèle financier unifié pour tous les services FareHarbor.

Comment FareHarbor percevra-t-il le paiement des réservations générées par API ? FareHarbor collectera automatiquement les paiements pour les factures de frais API en utilisant la méthode de facturation de votre tableau de bord. Les méthodes de collecte varient selon la région/devise :

• Euro (€) : Prélèvements automatiques SEPA. Suivez ces instructions pour configurer le SEPA.
• USD ($) (compte bancaire américain) : Prélèvements automatiques ACH. Sélectionnez votre compte ACH préféré sous Banque et paiements > Facturation.
• Autres devises et tableaux de bord avec PayPal comme seul processeur : Carte au dossier.

Pourquoi FareHarbor introduit-il ces frais ?

Nous introduisons ces frais pour couvrir l’investissement significatif requis pour maintenir et améliorer nos intégrations API avec les agences de voyages en ligne (OTA). Cela nous assure de pouvoir continuer à fournir des connexions fiables et efficaces et de développer de nouvelles fonctionnalités pour répondre à vos besoins évolutifs.

Quelles sont les réservations soumises aux frais API ?

Les frais API de 2 % s’appliquent aux réservations générées par API effectuées à partir de votre date d’entrée en vigueur (par exemple, le 1er mai 2024, pour les entreprises en Grèce).

Y a-t-il des exceptions aux frais API ?

Oui, les frais API ne s’appliquent pas aux éléments suivants :

• Réservations directes : Réservations effectuées directement via votre site web ou saisies manuellement dans FareHarbor.
• Réseau de distribution FareHarbor (FHDN) : Réservations de notre vaste réseau d’affiliés.
• Google Things to Do : Réservations provenant de la plateforme Google.
• Réservations AL-Desk.
• Boutons de réservation d’affiliés : Réservations effectuées via le système de FareHarbor intégré sur le site web d’un affilié.
• Réservations du portail affilié : Réservations générées par vos affiliés via leur portail dédié.
• Codes promotionnels affiliés : Réservations effectuées à l’aide de codes promotionnels spéciaux fournis aux affiliés.
• Réservations qui n’ont pas abouti via l’API.
• Réservations annulées.

Comment puis-je réduire mes frais API ?

Pour réduire vos frais API, nous vous recommandons de vous concentrer sur l’augmentation de vos réservations directes en ligne. FareHarbor offre divers services et ressources gratuits (comme le blog FareHarbor) pour vous aider à étendre votre présence en ligne et à augmenter les conversions.

• En savoir plus sur la connectivité API chez FareHarbor et nos dernières versions de fonctionnalités API sur cette page d’aide.
• Explorez des moyens d’augmenter vos réservations directes en ligne sur le blog FareHarbor.

Slack Channels

• #api-fee-global: used to share grouped updates about the global initiative
• #api-fee-questions: available for all employees to ask their questions related to the API Fee
• #api-fee-noram: used to share updates about rollouts in NORAM exclusively – will be closed after the end of the rollout
• #api-fee-apac + #api-fee-europe: historical data about the APAC and EMEA rollouts – archived

Calendar

Previous rollouts

In 2023-2024, the API Fee was rolled out to most of our clients as per this calendar:

In 2025, the API Fee was rolled out in the USA and Puerto Rico:

Eligibility

Eligibility will be based on the Processor Country (location of the bank account) of a dashboard.

• Processor Country is in a monetized region: Dashboard will be charged for the API fee.
• Processor Country is in a non-monetized region: Dashboard will not be charged for the API Fee.

Example: My company is based in the Netherlands but the Processor Country is in France. The API Fee will be effective March 15, 2024.

Exception: In LATAM/Caribbean, the vast majority of our clients are registered in a different country than where they physically operate due to Stripe’s limitations to verify these accounts and we therefore use the Dashboard Primary Location instead of the Processor Country.

API Fee structure

All clients are charged a 2% fee on API-generated bookings. The fee is calculated on the “Total Paid to Affiliate” which is the booking total including tax.

Commercial Exceptions

Enterprise clients and clients with a high volume of OTA TTV (typically, over $1M OTA TTV yearly) may be able to negotiate an introductory rate, also called Commercial Exception. Please get approval from your manager before offering a Commercial Exception and refer to the Commercial Exception Process Help Page for more details on how to submit one.

After approval in AppSheet, the Payment Operations team will be solely responsible for modifying changing rates in the dashboard. The team will follow the data present in the lead’s Custom Fields in Close.

The below exceptions are automatically granted:

• Guam and French Polynesia are exempted from the API Fee until further notice.
• USA/PR Paid Legacy FHS: For T2 & T3, the API Fee is waived for the full 2025. Their Effective Date is therefore January 1, 2026.
• Hawaii has a set pricing:
  • Tiers 0-2: No change – 2% fee, with no change to opt-in timing.
  • Tier 3: API Fee waived until end of October, set 1.5% fee from November 1, 2025 onwards. In case of a Paid Legacy FHS, the fee kicks-in in January 1, 2026.
  • Tiers 4 & 5: API Fee waived until end of October, set 1% fee from November 1, 2025 onwards.

Hawaii T3+ and Legacy FHS T2-3 Commercial Exceptions have been bulk-submitted on behalf of the AM team in AppSheet and should therefore appear in the API Fee Close CF.

Finding the API Fee

• In the FareHarbor Dashboard, under Advanced Settings -> Bookings -> API bookings. The field is only visible to FareHarbor Admin users, and only if ‘Allow API bookings’ is selected.
• In Close, in each shortname’s group Custom Field Group under API Fee & API Fee Update Date.
• In the AppSheet, only previously requested Commercial Exceptions will appear.

FareHarbor Rewards

In Portugal, France, Italy, Spain and Greece only, a select list of clients is eligible for a reward on total revenues (booking fee and API fees) generated according to the chart below (called “FareHarbor Rewards”). Outside of these markets, no FareHarbor Rewards will be granted.

How can I see which of my clients’ affiliates will be charged for?

While we are able to pinpoint affiliates whose bookings will typically be charged an API Fee for, some bookings might be coming manually for API affiliates and will therefore not be invoiced for.

To find the affiliates your client will be charged for:

1. Look at the clients’ affiliate list

   • Look at the list of affiliates under Settings > Affiliates
   • Look for all affiliates that have “API” in their Affiliate name

2. Run a booking source report by Availability Date, filter by Source: Network, group by Booking Created By, and discard bookings not generated via API.

Activations & Reactivations

Clients can opt-in to API Connectivity by:

• EMEA, APAC and NORAM Extended Markets: add a Billing Method
• USA/PR: Check the box “Allow API Bookings to be charged an API Fee”

Clients will need to request the Connectivity team to be connected via email at support@fareharbor.com.

Reconnections following a failed debit

Clients that were disconnected due to unpaid API Fee invoices and ask to be reconnected will need to get their invoices settled first. You can request a manual debit as follows:

1. Request the manual debit in #payment_operations using the workflow “Manual API Fee Debit Request”;
   1. In “invoices to debit”, add the Invoice ID found in Payment Processing Documents > Document ID. If there are several unpaid invoices, you can submit a single request and separate the several Invoice ID with a comma.
2. PayOps will debit unpaid invoices from the FareHarbor Dashboard (please debit and don’t do instalments as we can’t link those to invoices);
3. PayOps will click “Debit Done – Inform PayExp” which will post a message in #payment-experience-public. PayOps will add the Debit ID and Invoice ID in the thread of that new message.
4. PayOps will inform of the status of the debit:
   1. If debit fails, PayOps will reach out to the client to resolve
   2. If debit succeeds, PayOps will confirm to Connectivity who will in turn reconnect the client
   3. If debit status needs more time to update (i.e doesn’t succeed or fail straight away), PayOps will inform Connectivity who will in turn reconnect the client

Deactivations

Companies who do not wish to pay the API Fee can opt-out of API Connectivity, which requires the Connectivity Team to disconnect their API connections in their Dashboard.

1. Disconnecting API Connectivity:

* If the clients never used API Connectivity: uncheck “Enable API Bookings Creation” located in Advanced Company Settings. * If the client used API Connectivity previously: forward the disconnection request to the Connectivity team on their email at support@fareharbor.com. The Connectivity Team will disable permissions for API Affiliates connected to the Dashboard and leave the clients’ Billing Method active as we continue to charge the client for bookings initiated (booking date) prior to the opt-out date and completed (availability date) the month prior until no more API Bookings need to be billed for.

2. Notifying the API partners:

During a new region rollout: The Strategic Partnerships API team informs API Partners as follows:

• First email: on external comms date, a general memo is sent to all affected API partners, notifying them of the upcoming change;
• Second email: a few days after the disconnection date (the same as effective date), the specific list of clients that were disconnected is sent to each API Partner.

After a new region rollout: the Connectivity team member will inform the partner as part of the disconnection process.

Accounting calendar

1. On the 1st day of each month, API invoices are created automatically and immediately available in the Dashboard under Reports > Accounting > Payment Processing Documents.
2. On the 6th day of each month, clients are debited automatically on their Billing Method, provided the amount to debit is over the minimum threshold.
3. If the debit fails, the system will try again 7 days after the initial debit.

Invoicing

Invoicing eligibility

API Bookings are invoiced every 1st day of the month based on these variables:

• Booking was completed (availability date) between the first and the last day of the previous month.
• Booking was created (booking date) on or after the Effective Date in the clients’ region.
  • in the US, the Effective Date will be between April 1 and July 1 depending on the Tier.
• Booking was created by an API user.

Clients will be invoiced as follows:

• Active Clients using API Connectivity will be invoiced as per the logic above.
• Active Clients previously using API Connectivity who decided to stop will be invoiced every month for bookings initiated (booking date) between effective date and disconnection date, and completed (availability date) on the previous calendar month, until all eligible API Bookings have been invoiced. Offboarded Clients previously using API Connectivity will follow the same logic.
• For Active Clients who never used API Connectivity, no invoice will be generated.

Verify the invoice

Generate an API Bookings report using the API Fee Reconciliation Report in Reports > Accounting. The API Fee invoice amount is calculated off column “Total Paid to Affiliate”.

Updating business information on invoices

When clients update business details such as the owner name, tax ID, business name, or address on their FareHarbor Dashboard, these changes must be properly recorded to ensure that invoices reflect the most current information. Follow the instructions below to update these details and ensure they appear accurately on future payment processing invoices.

Updating the business tax ID

Clients can update their tax ID directly on the Dashboard or request assistance from a FareHarbor representative.

To update the business tax ID:

1. Navigate to Settings > Info and Policies > Logo & Contact.
2. Update the Tax ID field as needed.
3. Click Save changes.

Updating the business name and/or address

Clients can update their business name or address directly on the Dashboard or request assistance from a FareHarbor representative.

To update the business tax ID:

1. Navigate to Settings > Bank & Payments.
2. Click on Update within the second step (Enter customer verification information) of the Payment Setup Checklist.
3. Make the necessary changes to the business name and/or address.

Important note: Any updates made will appear on the next month’s invoice, not the current month’s one. If the update does not reflect in next month’s invoice, please escalate to Payment Operations (#payment_operations in Slack).

Debits

Debits are initiated on the 6th of each month for Dashboards with unpaid invoices. If a debit fails, the system will re-initiate a debit 7 days later.

Debit methods (a.k.a Billing Method)

• Dashboards processing in Euro will be automatically debited using SEPA Direct Debits.
• Dashboards processing in USD will be automatically debited using ACH Debits.
• All other currencies + PayPal-only dashboards will be automatically debited using Card on File.
  • All other currencies include AUD, GBP, NZD, etc…

Failed debits

See process for failed debits here.

Reconnecting a client following a failed debit

See in Activations & Reactivations.

Disputed Debits

In the case of a disputed debit, the payment method used to debit the disputed amount is invalidated and our team is no longer able to collect future invoice payment using that same mandate. The disputed payment status will also not change from “succeeded” to “failed” and it is hence not possible to debit again to recover the disputed amount as no amount shows as pending.

Fighting a disputed debit for PayOps

Disputes should be handled as usual by PayOps.

Recovering the disputed amount

The process to recoup the disputed funds from the client is as follows:

1. Upon reception of disputed debit notification from Stripe, PayOps will reach out to the client and:
   • Ensure they understand what the original debit was for,
   • Inform them that they need to reverify their billing method (it can be the same card/account),
   • Inform that FareHarbor will proceed with a debit of the disputed amount when this is done.
2. Once the billing method is reverified, PayOps will notify the @accounting team to reinitiate the payment using the workflow “Accounting Action Request” in #api-fee-global.
3. Once the debit is processed, PayOps will tag @payments-experience in the same thread to request them to link the new debit to the invoice.

Discrepancies

Flagging the discrepancy

To confirm a discrepancy, post in #api-fee-questions and we will confirm or help investigate.

Correcting the discrepancy: refund request

If a discrepancy was confirmed by our team, follow the process:

• If debit was not yet initiated:

  1. Notify @payments-experience to disable automated debits by tagging them in the Slack thread confirming the discrepancy.
  2. Submit a credit note + debit request in #api-fee-global using the workflow “Accounting Action Request”. The @accounting team will create a credit note for the AM to send to the client.
  3. The @accounting team will manually debit the correct amount using the Bank & Payments section and inform @ironbank of the manual debit ID to link to the invoice IDs for reconciliation purposes. This step will prevent our accounting system from trying to debit the invoice amount in the future.
  4. @payments-experience will link the debit to the invoice ID and re-enable automated debits for the affected company.

• If debit was already initiated: If the debit succeeded, follow the steps below. If it is still pending, wait until the status changes to succeeded or failed and act accordingly:

  1. Submit a credit note + refund request in #api-fee-global using workflow “Accounting Action Request”. The @accounting team will create a credit note for the AM to send to the client.
  2. The accounting team will then refund the client for the invoice difference using the Bank & Payments section.

Communicating the correction

1. The @accounting team will provide the Account Manager with a credit note highlighting the difference (adjustment) brought to the original invoice.
   • No new invoice with the correct amount can be issued in respect to the GAAP (Generally Accepted Accounting Principles).
   • The credit note will not be attached to the Payment Processing Documents section of the FareHarbor dashboard as uploading manual documents is not currently supported.
2. The Account Manager will be responsible for sharing the credit note with the client via email, using the “API Fee – Credit Note notification” template. The template will need to be edited before sending:
   • Add initial invoice ID from the dashboard, section “Payment Processing Documents” and the amount of that initial invoice
   • Add credit note ID provided by the @accounting team and the amount of that credit note
   • Add resulting amount to be invoiced by adding the invoice amount and the credit note amount (the latter should usually be a negative amount)
   • Attach credit note to the email as we are not able to attach it to the dashboard at this time

International bank transfer fees (APAC-specific)

Some companies in APAC might incur international transfer fees as we use our bank account located in Europe to debit API Fees, but rest assured that we debit in the local currency of the company. When these occur, FareHarbor is covering the international fee by issuing a reimbursement to the client. Proceed as follows:

• Collect client’s request, including a screenshot of the transaction stating clearly that the fee was incurred following the FH API Fee debit, and by how much.
• Send the request to @Rowena Dacanay via PM who will in turn submit the “Accounting Action Needed” workflow in #api-fee-global, pinging Christine Maedche for approval.
• Once approval is granted, Rowena will fill the reimbursement form tasking @accounting to credit the funds to the client’s bank account.
• If approved, the requesting team member will confirm the refund to the client.

Should this scenario spread across more markets, we will update the process.

Offboarded Companies

Offboarded Companies who previously used API Connectivity will continue to be invoiced and debited for until all eligible API Bookings have been charged. We will debit using the Billing Method available, and in case of no Billing Method present the @accounting team will use all means available to get payment as stated in our API Fee Terms.

Note: these additional payment methods require manual work and we are therefore not able to offer them as regular API Fee payment methods at this time.

Escalations

Please handle escalations as per usual practice.

Where are you currently charging? The API Fee has been introduced in all of our markets, except French Polynesia and Guam.

What is the API Fee covering? The API transaction fee covers the costs of setting up and maintaining the connections you have with OTAs (Online Travel Agencies) you work with, including expenses related to system maintenance, support, and infrastructure required to ensure smooth connectivity and improved services. A more exhaustive list is available on the API Fee Help Page.

What will change for me? I’m going to get the same service as when it was free. We are committed to increasing the pace of our support time, investing in improving our API connections and providing more dedicated service to you. More specifically, the API Fee allowed us to accelerate our development speed and release critical new- and updates to affiliate-specific features since its first launch in Portugal in 2023. A few examples of newer affiliate features:

• Airbnb API Integration – May 2025
• Custom Fields mapping for OTAs – Sept 2024
• Google ratings for External API – Q2 2024
• Reminder emails for API bookings – Q2 2024
• Affiliate rules introduction – Dec 2023
• Affiliate rules feature updates: capacity-based (Jul 2024), permanent affiliate restriction (Sep 2024), time of day (Oct 2024)

Why are you charging your clients and not the OTA? We develop API Connections and tailor our services based on our clients needs and feedback. Whether API connected or not, the OTA will still get their bookings and the API connection helps to dramatically ease the operations for your company to manage your distribution. OTAs are valuable partners we connect with to enhance your experience and share your direct feedback to help shape the future of these connections.

Why are you basing the fee on the total including tax? Bonus: It’s illegal. After deep research on the matter conducted by our legal team, we are charging the API Fee on the total including tax to align with industry practices.

Why are you charging a percentage and not a flat fee? The percentage aligns with all the rest of our pricing model. The booking fee, the payment link fee, the private event fee, everything is a percentage.

We also provide value in a myriad of aspects such as mapping connections, improving/strengthening our API, working closely with OTA to increase matching endpoints, looking for new partners, developing new features, improving these features etc… and we’ve been accelerating the speed of all of the above since August 2023, when we started charging the API Fee in Portugal and collected something to reinvest.

Our API is helping operators of all sizes and ticketing price, and finding the right the right amount for a flat fee would be a lot of guesswork and any number would be too much for smaller ticket prices, so we think a percentage is more fair to everyone. And charging a small flat fee wouldn’t allow us to provide all of the above at the quality we aspire to reach at some point.

Also while we are usually trendsetters, we are very late to the party as we are the last booking software to start charging for an API connectivity that is far superior to most competitors, and the only ones having a client-facing team dedicated to API questions.

How is the fee calculated? For companies subject to a 2% API Fee: If Company A gives 20% commission to an OTA and receives a $100 booking, $80 will be paid to the client, $20 will be kept by the OTA and the client will be charged $2 to pay to FareHarbor.

We understand the importance for businesses to take control of their online channels and establish meaningful connections with customers with the final option to maximize tickets sold and profitability. Our team is committed to supporting you in identifying opportunities and offering additional services that can enhance your online presence, enabling you to reach a wider audience and drive more conversions at the right profitability level. We believe that for tour providers, balancing both direct and OTA channels is crucial to 1) reduce risk, 2) maximize ticket sales and 3) drive profitability by tapping into a diverse customer base and leveraging the reach and marketing power of different channels. We are here to provide guidance and assistance every step of the way.

Can we negotiate the fee with clients who push back? At this time, we are only allowing an invited list of clients to negotiate the fee.

Can clients raise their rates on OTAs to cover the fee? If clients want to raise their rates on the OTA to cover the API fee we can give them the general guidance. First ask the client to please check their contract with the OTA if it actually has a parity clause. Second, it’s common knowledge that even if OTAs have a parity clause in their terms, they are not likely to enforce it. And if they do, they are likely to start with a warning. It’s up to the activity provider what to do with this info.

What happens if the client does not agree to the API Fee by their Effective Date? Will we charge for it anyway? We will be removing their API connectivity so bookings will not be able to be made via the API. Clients can still manually enter bookings in their FareHarbor Dashboard and tag the affiliate, but API bookings will not be able to be created, canceled or rebooked.

Invoicing & Reporting

How will the booking appear in the Dashboard? Bookings will appear as they normally do.

Will we base our fee out of OTA prices that come through the API or what we have set in the Dashboard? What is set in the Dashboard. With the implementation of pricing APIs coming this will eventually get fixed, but we’re confident prices are mostly accurate.

Will the API fee on bookings be included in the Reports section in FareHarbor’s internal report? The fee cannot currently be visible in reports, but they will see an invoice for the fee associated with their bookings in the Payment Processing Documents report.

Why is FareHarbor doing this?

FareHarbor builds its business model on a partnership and a win-win relationship with our clients. When making decisions that may impact you, we always consider how to align with your needs and strategies. Introducing the API fee ensures the alignment between FareHarbor’s overall strategy and your current and future goals. By charging a fee on API bookings, we can maintain and improve our level of service related to API connections. It’s important to note that you only pay the API fee if you utilize API connections and receive API bookings.

Why should I stay with FareHarbor now that you changed the API fee?

We understand the concern surrounding the API fee change, and we remain dedicated to your success. By introducing the API fee, we can maintain and enhance our level of service for API bookings. You will still benefit from a tailor-made dashboard, our high-converting booking system, our 24/7 technical support, and our range of free services to help you expand your online presence and boost online conversion!

As the largest reservation platform in the world, we offer access to over 20,000 vendors and more than 150,000 bookable activities.

Capterra and Phocuswright have rated us the #1 Tour & Activity Software, showcasing our commitment to excellence. With a team of over 800 employees across seven offices, we take pride in being a member of the Booking Holdings family.

Rest assured that your business is in capable hands, and we will continue to provide the highest level of service and support to ensure your continued success. If you have any further questions or require additional information, please don’t hesitate to contact our support team.

Can I absorb the booking fee now that you’re also charging me for API bookings?

We understand your concern about absorbing the booking fee. The introduction of the API fee was a decision made to maintain and improve our services for clients utilizing API connections. However, we still want you to succeed and generate as many bookings as possible directly through your website, which will not incur any cost. We encourage you to leverage our high-converting booking system, the powerful dashboard for managing your bookings, and our dedicated support team to optimize your online presence and maximize your revenue.

I always heard FH would never charge for your services because you only grow if I grow. How can I rely on you from now on?

We assure you that FareHarbor’s commitment to your growth remains unchanged. Our decision to introduce the API fee reflects our dedication to providing reliable and improved services to support your evolving needs. We still adhere to our partnership and win-win relationship, and our success is deeply intertwined with yours. We will continue to deliver a high-converting booking system, an exceptional dashboard and 24/7 technical support.

I want to disconnect the API immediately; which steps should I take?

If you wish to disconnect your API connection, please get in touch with our support team directly. They will guide you through the process and ensure a smooth disconnection of the API. We value your business and will provide the necessary assistance during this transition.

If you choose to disconnect immediately, the affiliate will send these bookings to you via email, and you will need to enter them manually into FareHarbor (our system). If you enter bookings manually, those bookings are not subject to the fee. To continue receiving API bookings in FareHarbor automatically, we recommend that you join FHDN or GTTD (Google Things to do). Joining these platforms will ensure seamless integration of bookings and save you the hassle of manual entry. Our support team can provide you with more details on how to join these platforms. By joining these platforms, you will ensure seamless integration of bookings and eliminate the hassle of manual entry. Our support team can provide you with more details on how to join these platforms.

I want to start accepting API bookings again; which steps should I take?

To get started with accepting API bookings, we recommend reaching out to our Support Team. We will be more than happy to assist you further with the necessary steps and provide you with a comprehensive understanding of our API connectivity options. They will work closely with you to ensure a smooth onboarding process and answer any questions you may have about the fees and pricing structure.

I feel cheated now that you’re changing your pricing model.

We understand that and we sincerely apologize for any negative emotions this changes may have caused. Our intention was never to deceive or betray your trust. The introduction of the API transaction fee was a decision made with careful consideration, aiming to enhance our services and better align with your evolving needs. We remain committed to your success and providing you with a high-converting booking system, an exceptional dashboard, 24/7 technical support, and the guidance of our Support Team.

Can you provide more details on the costs of managing clients working with OTAs and API integrations that the API transaction fee covers?

The API transaction fee covers the costs of setting up and maintaining the connections you have with the OTAs (Online Travel Agencies) you work with, including expenses related to system maintenance, support, and infrastructure required to ensure smooth connectivity and improved services.

More specifically, it will cover (but is not limited to) the human resources needed to ensure your connections are up to date, managed, accurate and flowing into one software for management in addition to things like downtime communications, help communicating with your Viator/GYG rep, ability to answer questions about those connections and other variables needed for a software and connections to continue performing so our clients don’t have to take care of it themselves.

How will the API transaction fee contribute to ensuring reliable connectivity and improved services for businesses?

The API transaction fee ensures reliable connectivity and improved business services by providing the necessary resources from FareHarbor to maintain and optimize the API infrastructure, helping to minimize disruptions, enhance system performance, and deliver a seamless booking experience for clients utilizing API connections.

Can you clarify the specific communication channels and advance notification methods used to inform clients about the API transaction fee?

We have transparently communicated the API transaction fee through various channels, including direct client communication via email and notifications within the FareHarbor dashboard. We have provided advance notification to ensure clients are well-informed about the fee and its implementation.

How does FareHarbor utilize the collected fees to support businesses with low online transaction volumes and enhance the services provided?

The collected fees from the API transaction fee support businesses with low online transaction volumes by enhancing the services provided. FareHarbor utilizes the collected funds to invest in system improvements, technological advancements, and customer support initiatives, ultimately benefiting these businesses and optimizing their experience with FareHarbor.

How will clients be notified about future updates or changes related to the API transaction fee?

We will communicate any updates or changes related to the API transaction fee through official channels. Clients can expect proactive communication and support who will address specific concerns and questions regarding the fee. Our commitment to transparent communication ensures that clients are well-informed about any updates or changes related to the API transaction fee.

Clients are asking if FareHarbor is financially stable because of all the recent pricing changes, how should I respond?

Reinforce that FareHarbor is continually investing in our people and our product. Last year alone we hired close to 120 employees, driven by our success and ambitious goals and never have had to do layoffs. We are reinvesting in our rapidly-growing Connectivity team and Engineering team due to increased demand for our industry-leading API services. Our recent product releases related to this service prove that we’re putting our money where our mouths are: affiliate rules, etc.