API Tiering Process
Last updated: June 16, 2025
The Strategic Partnerships Operations team tiers live API Partners every six months, so that Strategic Partnerships Managers – API Connections, Connectivity team and other teams working with these partners can work strategically and focus on quality leads. You can find more information about this process below.
The SP Ops team tiers API partners (including External, Channel APIs and Channel Managers) twice a year by looking at bookings made in the past 12 months. The update will be done in April and October.
Tiering criteria & metrics
Eligible Criteria: The API Partner has generated bookings in the past 12 months and the SP – API Partner Status custom field in Close is set to 7-Live.
Metrics:
The API Tiering Process includes a point system of total paid and API usage to determine the final partner tier. These are later weighted and combined to evaluate the partner’s final API tier.
- Total Paid – The amount of revenue processed through an API partner.
- API usage – The percentage of bookings made through the API versus manually entered into the Dashboard.
SP – API partner tier
Tier 1
- Total Paid is between $0 – $250,000.
Tier 2
- Total Paid: $250,000 – $999,999
- API usage:
- Between 0 – 10,000 total bookings and API usage is more than 81%
- 10,001 bookings and less than 50% API Usage
- Between 1,000 and 100,000 bookings, and more than 51% but less than 80% API Usage
Tier 3
- Total Paid: $1,000,000 – $19,999,999
- API Usage:
- Between 10,000 and 100,000 total bookings and above 80% API usage
- Above 100,000 total bookings and between 51-80% API usage
Tier 4
- Total Paid: $20,000,000 and above
- API Usage: above 100,000 total bookings and above 80% API usage
The Channel API Partners GYG, Viator, Expedia and Google will always be Tier 4.
How is SP Operations calculating API tiers (steps only for SP Ops)?
Phase 1 – Report & Google sheet structure
Every six months, the Strategic Partnerships Operations team starts the API Tiering process. This process is managed in a master Google sheet, which will be updated yearly.
Process to update the master Google sheet:
- Check if you have access to the API Bookings & In-System Affiliate Bookings report. If you don’t, reach out to your Manager or Strategic Partnership Operations to request access.
Go to the API Bookings & In-System Affiliate Bookings Report.
- On the right, select the following Booking Date toggle and set the date range for the last 12 months.

The report will refresh. You can now click on Download.
- Choose Crosstab as the file format. This type will open in CSV.
- Open the file in the master Google sheet.
Select all data on the spreadsheet and pivot the data in a new sheet.
- Part 1: Create a pivot (SP – Related should include all except the blank) with the following attributes. Add it to a new sheet, named Multi-currency Leads.
- SP – Related Leads
- SUM of #In-System Affiliate Bookings
- SUM of #API Bookings
- SUM of Total Paid
- Part 2: Create a pivot (SP – Related should be blank) with the following attributes. Add it to a new sheet, named No Related Leads.
- Affiliate Shortnames
- SUM of #In-System Affiliate Bookings
- SUM of #API Bookings
- SUM of Total Paid
Add new columns to the two new sheets in the same manner previous bi-annual Tiering was done (Total Paid and API Usage).
- The Points (Column F and I) formula should be copied over from previous bi-annual Tiering.
- Final Points will be a sum of column F and I.
Final Tier: copy the formula from previous bi-annual Tiering. The tiering will be based on the below table:
Tier 1 0 – 8 points Tier 2 9 – 18 points Tier 3 19 – 38 points Tier 4 39 points and above
- Part 1: Create a pivot (SP – Related should include all except the blank) with the following attributes. Add it to a new sheet, named Multi-currency Leads.
Important:
Filter the Total Paid. Any API Partners with a Total Paid value of $250,000 or below should immediately be assigned to Tier 1.
Channel APIs – Google, Expedia, GYG, Viator will always be Tier 4.
Example of a company where total paid is under $250,000:
Tours4fun (External API) has a Total Paid of $44,767.20, which is under 250,000.
Total Paid: Tier 1 (4 points)
Example of a company where total paid is above $250,000:
Tiqetsusd (External API) | Data Extracted from Tableau:
| Total Paid | SUM of #In-System Affiliate Bookings | SUM of #API Bookings |
|---|---|---|
| $8,143,110.21 | 329 | 95,619 |
| Criteria | Points | |
|---|---|---|
| Total Paid | $8,143,110.21 | 12 points |
| Sum of #In-System Affiliate and API Bookings | 95,948 | 12 points |
| Usage | 99.66% (95619/95948) | |
| Final Tier | 3 | 24 points |
Phase 2 – Comparison of the Close data vs. Tableau data
We need this step to determine which API Partners have not generated a booking over the last 12 months and to verify this information on the FH Dashboard.
Process to complete the comparison:
Report from Close:
- Search Close using this Query and export the data.
- Once the report is ready, import the report to a new sheet in the master Google sheet. Rename the sheet Close Data.
Move the custom.FH Shortname custom field to column C and insert two new columns:
i. Column D – Tableau vs. Close
ii. Column E – New Tier
Pivot the data from the Tableau Report to have the Affiliate shortnames in rows. Copy all the Affiliate shortnames to a new column as values.
- Do a V-lookup for the custom.FH Shortname custom field against the Affiliate Shortname from the Tableau Report in column D.
- Filter column D to see the shortnames that returned #N/A. Complete a spot-check of these shortnames on the Dashboard to see if any bookings were completed in the last 12 months.
- If no bookings were generated in the last 12 months, the API Partner will be a Tier 1. If a booking was generated, an investigation must be completed.
- For all API Partners with a match, complete a V-lookup on API Tiering from the Multi-currency Leads and No Related Leads sheets. Add this information to column E.
- Filter column E to see if there any #N/A, then investigate the reasons. If the reasons are common, include them in the notes column.
Additional: Channel Managers Tiering Process
The Channel API (also known internally as the Reseller API) enables seamless integrations between FareHarbor and online travel agencies (OTAs) such as Expedia and TripAdvisor Experiences (Viator). This guide explains how tiering works and how to determine a partner’s tier based on their total paid bookings over the last 12 months. How Tiering Works
Channel Managers API tiering is based on the Total Paid value across the past 12 months. This value determines the business tier for each partner, which is used internally to assess and manage OTA performance and engagement levels.
| Total Paid Range | Tier |
|---|---|
| $0 – $250,000 | 1 |
| $250,001 – $999,999 | 2 |
| $1,000,000 – $19,999,999 | 3 |
| $20,000,000 and above | 4 |
How to Calculate Tiers
- Open the Channel Manager Bookings Report in Tableau
- On the right panel, toggle Booking Date and set it to the past 12 months.
- Export the Bookings by Channel Manager report:
- Click Download
- Select Crosstab format (opens as a CSV)
- Open the downloaded CSV in the master Google Sheet.
- Add a new column called Final Tier.
- Use the following formula to calculate the tier: =INDEX(‘Total Paid Index’!$B$21:$B$28, MATCH(B2, ‘Total Paid Index’!$A$2:$A$9, 1)
- Once tiers are calculated, compare the new tier to the previous period to identify any changes.
- Once tier changes have been reviewed and confirmed, the next step is to proceed to Phase 3.
Phase 3 – Inform the API Managers, Close updates
Communication to SP Managers – API connections
Once the tiering process is complete, the SP Operations Team will send the SP Managers – API Connections a message with a link to a clean Google sheet, which will compare the old tiering to the new tiering. The following criteria should be used:
- If the API Partner tiered up, indicate with green.
- If the API Partner tiered down, indicate with red.
- If the API Partner remained the same, indicate with gray.
Close updates
The Strategic Partnerships Operations team will import a Google sheet with the API Partner’s shortname and tier. Only the main API Partner leads will be updated with the tier custom field. The multiple currency leads will not be updated. Here are the steps to update Close:
- Open a new Google sheet and rename it to the month of their API Tiering. For instance, “API Tiering – October 2023” (see image below).
- Rename column A to custom.FH Shortname.
Rename column B to custom.SP – API Partner Tier.

- From the File dropdown, download the spreadsheet as a CSV.
- Open Close and upload the CSV.
- Click Next and pay attention to the following:
- If a match is found, select Replace Lead Information in Close.
- If a lead doesn’t already exist, select Skip the Lead.
- Finally, click on Start Importing.
Connectivity Expectations for Live API Partners (Based on Tier)
Tier 1 – basics
- Pulls availability
- Pushes bookings
- Can cancel or rebook through the API
- Honors our rate limit (approximately 3100 requests per 5 minutes)
- Routine refresh periods as laid out by the Partnerships team
- Make requests to populate or update their cache with general availability data for the current and next couple of months (or further into the future) at least twice a month.
- Make requests to update their cache with availability data for the current week (and perhaps next week or next few weeks) at least three times a week.
- Make requests to update their cache with availability data for the current day (and perhaps next day or next few days) several times a day.
Tier 2
- Includes Tier 1 criteria
- Able to accommodate per group AND per person pricing on their platform
- Displays customer type minimums and maximums (not just availability capacity)
Tier 3 and Tier 4
- Includes all Tiers 1 and 2 criteria
- Connects to FareHarbor Custom Fields
- Connects to Transportation Module
- Note: Tier 4 consists of mostly Channel Partners, for which these do not always apply.
Strategic Partnerships Expectations for Live API Partners (Based on Tier)
Tier 1 – Basics
- Bi-annual business review / phone call
- How are they performing?
- API Success metrics (provided in support by Connectivity):
- % of bookings made through API vs manual
- Growth in supply/items available
- Support tickets/time & top support ticket categories
- What do they need from us?
- What do we need from them?
- Technical Improvements
- Business Improvements (What are they doing to market our clients? Do they have a clearly defined niche?)
- FHDN API plug (for API affiliates where there is overlap/potential)
- If they are on FHDN API:
- What markets do they sell things to do in?
- What types of experience do they sell?
- Where is there any untapped overlap (based on their sales and the previous two questions?
- Requests / feedback (i.e. API or Inventory related)?
- What volume can we expect in the next half of the year/next year?
For FHDN API Partners Only:
- Quarterly newsletter
- Updates to FHDN API / new inventory available
- Best practices for working with FHDN API
Tier 2
- Includes Tier 1 criteria plus the following:
- Co-Marketing:
- Is our logo & company description on their suggested rez system page (if applicable?)
- Are there opportunities for LinkedIn/social media/blog content cross promoting our partnership? Bonus if through FHC!
- API Success Metrics:
- Identifying specific endpoints that they aren’t using and creating a plan to implement together. Especially if those are creating support bottlenecks, i.e., pricing and/or custom fields
- Quarterly business review/call
- Co-Marketing:
Tier 3 and Tier 4
- Includes tier 1-3 criteria
- For FHDN API Partners include a Monthly FHDN API update (phone or email) that can be automated in the future.
Additional information
Process to tier new API Partners
When an API Partner goes Live, the SP Operations team will be informed on the #connectivity-extapi channel. The SP Operations team will look at the bookings generated over the past 12 months with the API Usage. Once the tier has been determined, the SP Operations team will inform the SP Manager prior to updating Close.
Changing an API tier
Tiers should only be updated by SP Operations. If there is a lead that appears to be incorrect based on the information above, please set a task for SP Ops in the Close lead.
FHDN API tiering process
Due to limited information, FHDN API Partners will not be part of the initial tiering process. This is a future project for the SP Operations team.