Viator API Documentation & Specification – Merchant Part

{
  "service_type": "platform",
  "base_url": "https://docs.viator.com",
  "auth_method": "api_key",
  "auth_config": {
    "notes": "Viator Partner API uses API key authentication issued to approved partners. Exact header/param name not determinable from provided excerpt."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Viator operates an affiliate/partner model, typically commission-based rather than direct API subscription pricing. Confirmation not possible from provided content."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "travel and tours marketplace",
    "merchant partner integration",
    "product catalog access",
    "booking and reservation flow",
    "support procedures documentation"
  ],
  "raw_analysis": "Viator is a travel experiences and tours marketplace (owned by TripAdvisor) that exposes a Partner API. The provided page is the 'Merchant' portion of the official Viator Partner API documentation hosted at docs.viator.com. The scraped content is almost entirely CSS/HTML boilerplate (style tags, figure styling) rather than substantive documentation, and the anchor '#support-procedures-merchant' suggests the relevant content is a 'Support Procedures' section for merchant partners within a larger single-page or multi-section API specification. Consequently, no concrete endpoint paths, request/response schemas, authentication header names, or rate-limit values could be extracted. This is clearly a real, production-grade platform API used by travel affiliates, OTAs, and merchant partners to search, book, and manage tours and activities inventory. The intended audience is developers at partner companies (merchants, resellers, affiliates) integrating Viator's inventory into their own booking flows. Maturity is high — Viator is a well-established brand with versioned public API docs, runbook-style support procedures, and structured partner onboarding. Integrations typically include white-label booking engines, affiliate storefronts, and OTA feeds. Access is gated: developers generally must register as a Viator partner and receive API credentials (key/secret) before using endpoints. To produce a usable builder spec, the full rendered documentation page (or the underlying OpenAPI/Swagger file, if published) would need to be fetched rather than this CSS-heavy excerpt."
}

2/3 tests passed

```json
{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 5.0,
    "response_parseability": 7.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 4.0,
    "latency": 9.5,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "model": "affiliate/partner commission-based",
    "notes": "Viator operates a partner/affiliate model with commission-based revenue rather than direct API subscription pricing. Exact rates not retrievable from provided content.",
    "predictability": "medium",
    "agent_recommendability": "conditional — requires partner application and approval"
  },
  "issues": [
    "No public pricing page — commission structure hidden behind partner onboarding",
    "llms.txt returns 403 AccessDenied, blocking LLM-friendly machine-readable discovery",
    "robots.txt disallows key technical/API documentation paths (/partner-api/*/technical/), hampering agent-indexable docs",
    "Partner/merchant onboarding requires application and approval — not self-serve",
    "No clear programmatic auth flow documented (API keys, OAuth) in provided checks",
    "Site is served as a 'saved from' HTML mirror, suggesting possible stale/mirrored docs rather than live dynamic content"
  ],
  "recommendations": [
    "Publish a public llms.txt describing capabilities, auth, and endpoints for AI agent discovery",
    "Open robots.txt for technical doc paths (or provide a machine-readable index) so agents can parse integration guides",
    "Add a self-serve sandbox signup with instant API keys to improve first-try success",
    "Document auth model explicitly (API key vs OAuth) and error code taxonomy",
    "Expose a public pricing/commission overview to enable agent-side cost comparison",
    "Ensure docs are served live (not a static mirror) and versioned via stable URLs"
  ]
}
```