---
title: "Wego: Affiliate, Distribution and Provider Boundaries"
description: "Separate Wego affiliate search, distribution and provider roles; diagnose rate retrieval, access and handoff failures with operational checks."
slug: "wego"
translationKey: "platform-wego"
locale: "en"
type: "profile"
category: "multi-vertical-metasearch"
platform: "Wego"
domain: "wego.com"
tags: ["wego","flight","hotel","affiliate","api","oauth","deep-link"]
vertical: ["flight","hotel"]
featured: true
publishedAt: "2026-09-19"
updatedAt: "2026-09-26"
reviewedAt: "2026-09-26"
directory: {"status":"active","reviewedAt":"2026-09-26","platformType":"metasearch","audiences":["b2b","b2c"],"businessModels":["affiliate"],"integrationMethods":["api","deep-link"],"docsUrl":"https://developers.wego.com/docs/affiliate/get-started/","guideTranslationKey":"integration-wego-affiliate-api","sources":[{"title":"Wego Developers Portal","url":"https://developers.wego.com/"},{"title":"Wego Affiliate API — Get Started","url":"https://developers.wego.com/docs/affiliate/get-started/"}],"roles":["metasearch","comparison-engine","travel-marketplace"],"ecosystemLayers":["retail-discovery"],"turkeyRelevance":"global-context","directSupplierParticipation":"unknown","developerDocsAvailable":"unknown"}
sources:
  - title: "Wego Affiliate API — Get started"
    url: "https://developers.wego.com/docs/affiliate/get-started/"
  - title: "Wego Affiliate API — Flights"
    url: "https://developers.wego.com/docs/affiliate/guides/flights/"
  - title: "Wego Affiliate API — Hotels"
    url: "https://developers.wego.com/docs/affiliate/guides/hotels/"
  - title: "Wego Distribution"
    url: "https://developers.wego.com/docs/distribution/getting-started"
  - title: "Wego Providers"
    url: "https://developers.wego.com/docs/provider/welcome"
---

Wego's developer ecosystem separates consuming search, distributing travel products and supplying offers to the marketplace. Treat the chosen relationship as part of the architecture: it determines access, data ownership and the point at which a traveler becomes a booking customer.

This profile explains those decisions. Use the [Wego Affiliate API integration guide](/en/integrations/wego-affiliate-api) for request/response examples and adapter implementation.

## Production scenario: one result is mistaken for all offers

In a fictional hotel search, the result card shows one attractive rate. The application labels that provider the only available seller, although additional rates have not been retrieved. A traveler then lands on a different room condition than expected.

Start by identifying the response's level of detail. The [hotel guide](https://developers.wego.com/docs/affiliate/guides/hotels/) describes a best-rate view and retrieval of additional rates. A summary is not proof of complete provider coverage. Preserve the chosen property, room conditions, guests, rate and seller as separate identifiers.

## Choose the participation model

| Relationship | Official entry point | Decision to establish |
|---|---|---|
| Affiliate | [Get started](https://developers.wego.com/docs/affiliate/get-started/) | Consume search and hand off using the supported links |
| Distribution | [Distribution guide](https://developers.wego.com/docs/distribution/getting-started) | Confirm enabled scopes and transaction capabilities |
| Provider | [Provider portal](https://developers.wego.com/docs/provider/welcome) | Supply offers for consideration in Wego results |

The profile's directory facts describe the affiliate API and deep-link flow. They do not enumerate every commercial arrangement offered by Wego.

An affiliate account is not automatically a distribution account. The Distribution documentation separately describes account scopes and hotel booking capabilities. Establish who accepts the order, handles payment and services changes for the actual flow rather than applying affiliate handoff assumptions to every Wego product.

## Access, user intent and credentials

The affiliate [onboarding page](https://developers.wego.com/docs/affiliate/get-started/) requires contact for credentials, real-user searches and Wego links to partners. Access includes traffic-quality obligations as well as technical limits. Confirm the current rules for the client rather than treating an example limit as a permanent SLA.

Obtain access tokens on the backend and avoid shipping credentials to the client. In your application, distinguish authentication failure, missing entitlement and exhausted capacity. Retrying a denied account cannot repair its permissions.

Choose an explicit owner for partner configuration, token handling and incident escalation. A content publisher and an inventory supplier may need different operating teams even when they share a company name.

## Search lifecycle and vertical models

The [flight guide](https://developers.wego.com/docs/affiliate/guides/flights/) separates search creation, result retrieval and additional fares for a trip. Keep trip identity distinct from the fare and provider selling it.

For flights, preserve segments, carrier roles, passenger types, cabin, fare conditions and baggage where available. For hotels, preserve property, room/rate, occupancy, meal, cancellation and mandatory charges. A generic amount cannot express both products safely.

Show partial results without claiming completion. Bound polling and cancel abandoned work according to your application policy. Keep the selected offer stable when later results arrive. The linked integration guide covers the provider-specific retrieval details; this profile does not define substitute wire schemas.

## Handoff and transaction evidence

Use the supported Wego handoff URL for the affiliate flow. Replacing it with a reconstructed seller homepage can lose both travel context and attribution. Test dates, passenger/guest counts, currency and chosen provider in a clean session.

Keep search, selection, redirect and confirmed order as separate observations. A click does not prove checkout completed. For a distribution booking flow, also define how an ambiguous response is reconciled before retrying an order; do not infer booking idempotency from search behavior.

## Failure modes and recovery

| Symptom | First evidence | Recovery direction |
|---|---|---|
| Only one hotel rate is shown | Summary versus additional-rate retrieval | Retrieve the appropriate detail |
| Same flight has conflicting prices | Trip, fare, provider and conditions | Preserve commercial options |
| Results repeat after polling | Search ID and retrieval/merge state | Repair the adapter's state handling |
| Affiliate link loses the selected stay | Original handoff and landing context | Restore supported URL continuity |
| API works for one product only | Account scopes and contract | Verify entitlement before retrying |
| Booking outcome is unclear | Order reference and transaction evidence | Reconcile through the applicable booking flow |

These are recommended internal categories, not provider error codes. Preserve enough redacted context for the responsible team to reproduce the incident.

## Operational metrics and release checklist

Track valid started searches, searches yielding useful results and eligible outgoing clicks separately. Align search-to-click reporting with the partner's definition. Do not count polling calls as new user searches in your own funnel.

Measure equivalent successful landings over eligible samples, split by vertical, seller and failure reason. Track additional-rate retrieval failures separately from empty hotel inventory. Treat unknown conditions as data gaps rather than favorable values.

Test partial results, additional fares/rates, missing entitlement, expired authentication, changed offer and broken handoff. Confirm that provider, affiliate and distribution configurations cannot be accidentally exchanged. These controls are engineering recommendations; the current partner contract and official documentation define supported behavior.