Operator Onboarding: Send Guests to Checkout or Apply for API Access
“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.”
Choose Send guests to our checkout to onboard one tour with your existing hosted checkout link for the New Orleans pilot (starting with Jean Lafitte's covered swamp tour with transportation, item 763318), or choose Apply for API booking accessto route through our full direct API intake. Intake is strictly limited to business and product details—arrange any credentials through the provider's approved secure process.
Send Guests to Your Checkout · Or Apply for API Booking Access
Select Send guests to our checkout to add a single tour offer and review affiliate, pickup, and payout terms, or select Apply for API booking access for direct API integration review.
mode=qa_live_test)The pre-loaded Jean Lafitte Swamp Tours (Item #763318) example below is a read-only sample preview. Opening or inspecting this public preview never creates an onboarding application or writes to the attribution ledger. Real operators can click Enter Your Own Tour (Live Intake) to submit a tour.
Approve the FareHarbor affiliate connection for this specific offer and confirm the eligible hotel pickup stops.
In FareHarbor Dashboard → Settings → Affiliates / ASN, authorize our affiliate account for item #763318 and confirm the French Quarter & Downtown hotel pickup list.
Approve the affiliate connection for that specific offer
Authorize our FareHarbor affiliate account (welcometoneworleanstours or aktourcenter) for item #763318 (Covered Swamp Tour with Transportation) so is_affiliate_rules_applied is active on the ASN price sheet.
Confirm the eligible pickup stops
Confirm the eligible French Quarter & Downtown hotel pickup stops on FareHarbor custom field #12258400 (including Hotel Monteleone, 214 Royal St — #22056428) and pickup lead times before departure.
Record affiliate account, commission, refund treatment, payout timing & referral booking record delivery
Reuse the existing DCC review queue to record the confirmed affiliate account, commission rate, refund/cancellation treatment, payout timing, and how we receive a booking record carrying online_booking_references (<placementId>-clk_<24hex>).
Recorded in Existing Review Queue (earthosControlMapFindings) — Sample Schema:
Checkout, Seat Availability, Commission Terms & API Booking Tracked Separately
Jean Lafitte (763318) starts with Checkout tested, Check seats at FareHarbor, Commission terms pending, and API booking requires approval. Each status changes only when we have evidence for that specific capability.
Checkout tested
Mobile checkout journey verified through FareHarbor item #763318 final review screen (2026-11-18, 2 adults, Hotel Monteleone pickup #22056428, $124.00 subtotal + $7.44 fees = $131.44 total) with referral tracking parameters.
When it changes: Changes to 'Checkout tested' when an end-to-end checkout walkthrough verifies date, party size, option, pickup stop, price breakdown, and referral tag pass-through.
Check seats at FareHarbor
FareHarbor calendar feed lists open departure time slots (08:30 / 10:00), but omits numeric remaining seat count in the public calendar feed; guests check remaining seats at FareHarbor.
When it changes: Changes to 'Live seat count verified' only when a provider feed or authorized API response confirms numeric remaining seat capacity.
Commission terms pending
FareHarbor item #763318 currently returns is_affiliate_rules_applied: false; awaiting operator confirmation of the affiliate account, commission rate, refund treatment, payout timing, and referral booking record delivery.
When it changes: Changes to 'Commission terms confirmed' when the reviewer records the confirmed affiliate account, commission rate, refund treatment, payout timing, and booking record delivery method.
API booking requires approval
Guests are sent to Jean Lafitte's hosted FareHarbor checkout; native API booking creation requires separate provider-approved API credentials and end-to-end verification.
When it changes: Changes to 'API booking approved' only when provider-approved API credentials are arranged through the secure process and booking write access is verified.
How One Application Moves From Submission Through Review & Checkout Attribution
Public preview serves labeled sample data (sample_onb_jean_lafitte_763318_demo) and leaves the live application queue and attribution ledger untouched. The live end-to-end test runs behind authenticated QA (mode=qa_live_test).
Stage 1 · Sample Submission (Initial State)
Jean Lafitte Swamp Tours · Item #763318 (Sample)
- • Checkout: Checkout tested
- • Seats: Check seats at FareHarbor
- • Commission: Commission terms pending
- • API: API booking requires approval
Stage 2 · Sample Review Record (Illustrative)
Affiliate + Pickup + Payout Terms Recorded
- • Affiliate:
aktourcenter(15% ASN — Sample) - • Pickup: Hotel Monteleone (#22056428)
- • Commission: Commission terms confirmed (Sample)
- • Seats & API remain Check seats at FareHarbor / API booking requires approval
Stage 3 · Sample Referral Trace (Read-Only)
Matcher + Click Redirect + Attribution Format
Placement nola-hotel-monteleone-demo-pilot routes through /api/v1/ads/click to FareHarbor item 763318 with sample ref=nola-hotel-monteleone-demo-pilot-clk_000000000000763318de0001.
Required Verification Before Switching from Viator to Direct API
We keep an operator's existing verified Viator booking channel active until all seven verification gates pass. Commission never determines traveler suitability or recommendation ranking.
1. Operator Permission
Explicit authorization from the tour or transportation company.
2. Agreed Commercial & Settlement Terms
Signed 10% direct commission and settlement agreement (kept separate from onboarding applications).
3. Securely Arranged Credentials
Provider-approved API credentials arranged securely after review—never via public forms or email.
4. Exact Product & Option Mapping
Verified mapping between DCC references and the operator's native API product/option IDs.
5. Current Prices & Live Availability
Live API responses verified for real-time seat inventory, schedules, and retail pricing.
6. Reliable Attribution & Outcome Reporting
End-to-end verification of booking references, confirmations, cancellations, and settlement reporting.
7. Cancellation & Cruise-Return Policies
Verified separately for direct bookings; Viator marketplace guarantees do not automatically carry over.
GoSno · Rezdy Native REST API v1
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.
pending until DCC-side integration credentials and end-to-end tests are completed.Provider-Specific API Architectures (Not All Systems Use OCTO)
We inspect the actual API documentation for each booking system rather than assuming FareHarbor, Bókun, Rezdy, and other native APIs all use OCTO endpoints.
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.