Skip to main content
For Tour & Transportation Operators Worldwide10% Direct API Commission Model

Direct API Partnerships for Tour Operators

“It’s time tour operators kept more of every booking. Connect your existing booking system to DCC through an authorized API. Our commission is 10% on completed direct bookings we generate.”

Destination Command Center (DCC) is a source-backed travel decision engine that helps travelers check schedule constraints, logistics, and cited evidence before choosing how to spend their trip. We welcome tour, excursion, and transportation operators worldwide—while keeping global partnership eligibility distinct from our current curated destination coverage.

How Our Operator Partnership Works

Clear Channel Attribution, Explicit Permission, and Neutral Decisions

We separate initial marketplace referrals from direct API connections, verify every integration against the provider's actual API documentation before switching channels, and never let commercial terms influence traveler suitability rankings.

1 · Worldwide Eligibility vs. Coverage

We Welcome Operators Worldwide

Operators in any region can apply for a direct API connection. We keep global partnership availability distinct from DCC's current curated destination reference guides (currently live for Juneau, Red Rocks, the Denver–Breckenridge corridor, and New Orleans).

2 · Initial Booking Channel

Verified Viator Products First

Verified Viator products (matched by exact supplier reference and confirmed active via Viator's API) can provide the initial booking channel. Each page clearly discloses that bookings currently go through Viator and never implies the operator has already agreed to a direct partnership.

3 · Requirements to Switch Direct

Four Gates Before Direct Cutover

Switching from Viator to direct bookings requires: (1) explicit operator permission, (2) provider-approved API access, (3) signed commercial and settlement terms (the proposed 10% is separate from signed terms), and (4) a verified end-to-end integration.

4 · Non-Exclusive Distribution

Keep Your Existing Sales Channels

Operators keep their existing website checkout, Viator listings, OTAs, and local reseller relationships. Connecting an authorized booking API to DCC adds a direct booking option without requiring exclusivity.

5 · Editorial Independence

Commission Never Affects Ranking

Commission never determines traveler suitability or recommendation ranking. DCC evaluates schedules, transfer buffers, public/free alternatives, and operator options using the same neutral criteria regardless of booking channel.

6 · Policy & Guarantee Separation

Separate Policy Verification

Cancellation terms and cruise-return policies are verified separately for each direct integration. Marketplace protections (such as Viator's Worry-free Shore Excursion guarantee) apply only to qualifying Viator bookings and do not automatically carry over to direct bookings.

Explore island and coastal operators

Dated sources, selected tour listings and practical questions to check before choosing an experience.

First Direct-Channel PilotRezdy Native REST API v1

GoSno (Denver to Breckenridge & I-70 Mountain Corridor, Colorado)

GoSno operates its own Rezdy-backed private transfer checkout on gosno.co and publishes a live /.well-known/dcc manifest. Separately, GoSno is the first candidate for DCC's 10% direct-channel API pilot. While gosno.co's own storefront endpoints respond in production, DCC-side Rezdy API credential provisioning, DCC-side live bookable slot verification, and the 10% commercial addendum remain pending.

Open GoSno Operator Profile →

1 · Existing GoSno Storefront Integration (gosno.co — Operational & Unchanged)

Operational on gosno.co: GoSno's own storefront checkout (gosno.co/breckenridge and gosno.co/vail), /.well-known/dcc manifest, and /api/dcc/routes catalog are active in production for 100% private transfers.

Captured Live Endpoint Evidence (2026-10-30T10:56:31.488Z):

• GET /.well-known/dcc → HTTP 200 (GoSno LLC, CO PUC LL-03577)

• GET /api/dcc/routes → HTTP 200 (9 private SUV routes, e.g. DEN-BRECKENRIDGE → P7477S)

• GET /api/availability (2026-12-15) → HTTP 200 (suv.available=false, van.quoteOnly=true)

2 · New DCC 10% Direct-Channel Pilot Status (DCC-Side Integration — Pending)

  • • Operator Authorization & DCC-Side Rezdy API Access: pending / pending
  • • DCC Product Mapping & Live Price/Availability: pending / pending
  • • 10% Direct Commercial Addendum & Outcome Reporting: pending / pending
  • • Separate Direct Cancellation Policy Verification: pending
  • • GoSno operates its own gosno.co storefront and /.well-known/dcc manifest (CO PUC LL-03577); formal authorization for the new DCC 10% direct-booking pilot is pending.
  • • Rezdy API access is active inside GoSno's own gosno.co deployment, but DCC-side REZDY_API_KEY credentials for api.rezdy.com/v1 have not yet been provisioned in DCC.
  • • Proposed 10% direct commission addendum and settlement terms are not yet signed.
  • • GET https://gosno.co/api/dcc/routes returns HTTP 200 with 9 outbound DEN private SUV route offerings mapped to Rezdy product codes (e.g., DEN-BRECKENRIDGE -> P7477S at $399.00; DEN-VAIL -> PSW87A at $499.00; DEN-COPPER -> PF773R at $399.00, whereas gosno.co/llms.txt lists Copper at $449). Separately, GET https://gosno.co/api/public/route-feed lists 4 DEN ↔ Breckenridge records (SUV P7477S/PNK8J0 at $399 and Van PKQDPG/PWWQL7 at $599 up to 10 passengers), while /api/availability marks vans quoteOnly: true.
  • • Live probe GET https://gosno.co/api/availability?origin=DEN&dest=Breckenridge&date=2026-12-15&time=10:00&vehicleClass=suv&tripType=one_way&direction=to_mountain returned HTTP 200 with suv.available=false and van.quoteOnly=true; DCC-side live bookable slot verification against Rezdy is pending.
  • • End-to-end DCC booking hold, confirmation, cancellation, and commission outcome reporting are pending.
  • • Direct-channel cancellation terms and winter I-70 operational policies are pending separate verification for the DCC direct pilot.
Verified DCC Operator Pages · Initial Viator Booking Channel

Operators Currently Featured Through Verified Viator Listings

We only list a company here when its DCC operator page, supplier identity (SUPPLIER-...), verified destination reference, and unmodified Viator product URLs have been verified against preserved Viator Partner API v2 responses. These pages currently route bookings through Viator; none of the Viator-channeled operators below are claimed as enrolled direct API partners unless verified and switched.

New Orleans, LouisianaCurrent Channel: Viator (2 Verified Active)

Cajun Encounters Tour Co.

Operates guided flat-bottom boat tours through the Honey Island Swamp in Slidell, Louisiana, with self-drive and New Orleans shuttle options.

Official Website: https://www.cajunencounters.com/

Viator Supplier Reference: SUPPLIER-Ls68Tv9wCH9YKPX1YdQD0g==

Verified Active Viator Products: 6953SWAMP, 6953SWAMPTRANS

LaPlace & New Orleans, LouisianaCurrent Channel: Viator (2 Verified Active)

Cajun Pride Swamp Tours

Operates covered swamp boat tours on a private wildlife refuge along the Manchac Bayou in LaPlace, with self-drive and New Orleans shuttle departures.

Official Website: https://www.cajunprideswamptours.com/

Viator Supplier Reference: SUPPLIER-ah695t/3pUZ5JxgMe0brVQ==

Verified Active Viator Products: 141126P1, 141126P2

New Orleans, LouisianaCurrent Channel: Viator (3 Verified Active)

Haunted History Tours

Operates guided evening walking and bus tours in the French Quarter and historic New Orleans neighborhoods focusing on documented history, legends, and architecture.

Official Website: https://hauntedhistorytours.com/

Viator Supplier Reference: SUPPLIER-xe2YbZ42ogLOrNtIzC5ybg==

Verified Active Viator Products: 3252_1, 3252_5, 3252P9

New Orleans, LouisianaCurrent Channel: Viator (3 Verified Active)

Doctor Gumbo Tours

Operates small-group culinary and craft cocktail history walking tours across the French Quarter and Treme in New Orleans.

Official Website: https://www.doctorgumbo.com/

Viator Supplier Reference: SUPPLIER-uhTuEGs0R00a22vvRVDMHg==

Verified Active Viator Products: 6484NOLAFOOD, 6484P3, 6484FRQCK

Lafitte & New Orleans, LouisianaCurrent Channel: Viator (1 Verified Active)

Airboat Adventures

Operates small and large airboat swamp tours departing from Jean Lafitte, Louisiana, with optional New Orleans hotel pickup.

Official Website: https://airboatadventures.com/

Viator Supplier Reference: SUPPLIER-7eNlteakiwgCVdiaT3VQkg==

Verified Active Viator Products: 6455NOLAAIR

Provider-Specific Technical Verification

Actual Reservation APIs — No Assumed Universal Compatibility

Reservation systems use different native endpoints, authentication headers, and booking lifecycles. We do not assume FareHarbor, Bókun, Rezdy, and other native APIs all use OCTO endpoints, and we do not claim universal compatibility before inspecting the provider's documentation and verifying a live integration.

Rezdy (Supplier / Agent REST API v1)

Native REST JSON (v1)

Auth: apiKey header / query parameter issued per authorized supplier/agent connection

GET /v1/products, GET /v1/availability?productCode=...&startTimeLocal=...&endTimeLocal=...

POST /v1/bookings with internal reference/reseller tracking; used by GoSno's gosno.co storefront and evaluated as DCC's first direct-channel pilot candidate.

FareHarbor (External API v1)

Native REST JSON (External API v1 — NOT OCTO by default)

Auth: X-FareHarbor-API-App and X-FareHarbor-API-User headers with operator-authorized company shortname

GET /api/external/v1/companies/{shortname}/items/, GET .../items/{pk}/availabilities/date/{date}/

POST .../availabilities/{pk}/bookings/ with partner/affiliate voucher & note fields; requires explicit operator permission for the company shortname.

Bókun (REST API / Channel Inventory API)

Native REST JSON with HMAC-SHA1 request signing (separate from optional OCTO adapter)

Auth: X-Bokun-Date, X-Bokun-AccessKey, and X-Bokun-Signature (HMAC-SHA1)

GET /activity.json/{id}, GET /activity.json/{id}/availabilities?start=...&end=...

POST /booking.json/activity-booking/reserve-and-confirm with externalBookingReference for commission settlement.

Ventrata / OCTO Core v1.2.0

OCTO Core REST JSON (for providers that explicitly implement OCTO)

Auth: Authorization: Bearer <token> with Octo-Capabilities header

GET /suppliers, GET /products, POST /availability

POST /bookings (hold) and POST /bookings/{uuid}/confirm with resellerReference for outcome reporting.

Direct partnerships are API-only. If an operator does not have authorized API access, we cannot switch bookings to a direct connection, and existing verified listings can continue through Viator.

Submit API Onboarding Details →