Μετάβαση στο περιεχόμενο

Αυτό το περιεχόμενο δεν είναι ακόμη διαθέσιμο στη γλώσσα σου.

For Builders

Build hotel commerce into your product.

API-first hotel commerce: search, booking, payment, 64+ webhooks, attribution and AI handoff — with a hosted MCP server so agents read the live contracts, and Booking Engine fulfilling underneath.

See documentationRequest API access
REST + OAuth2 + SDKs Hosted MCP server 64+ webhook events
wink · agent integration live

# 1 · connect an agent or coding client

$ claude mcp add wink

https://api.wink.travel/mcp --transport http

→ browser sign-in at iam.wink.travel

✓ connected · OAuth2 + PKCE · no client secret

# 2 · find the operation, read the live contract

api_search "create booking"

→ POST /bookings · wink://api/operation/createBooking

# 3 · create the booking, take payment

$ wink bookings create --rate rp_8421

201 · #WK-2X9F · paid via Wink

# 4 · react in real time

on booking.created → fulfill & reconcile

What can developers build with Wink?

Developers can build hotel search, booking, payment, webhook, attribution, reporting, AI handoff and embedded commerce workflows into approved products. Wink developer access works with hotel-controlled supply from Extranet, partner context from the underlying network, AI handoff through Agentic AI, and Booking Engine fulfillment for hotel-specific checkout, payment, confirmation and booking completion.

Who it’s for

For teams building hotel commerce, not just reading docs.

Developer access fits product, engineering, AI, platform and operational teams. Evaluating an integration for an AI product, bank or super app? See For Platforms & AI.

Product teams

Add hotel commerce to an existing app or platform via developer access + Booking Engine.

AI product teams

Route assistant-led hotel intent into controlled booking flows with Agentic AI and the MCP server.

Agencies & DMCs

Build custom storefronts, booking flows or itinerary products with Web Components.

Channel manager / PMS

Coordinate availability, rates, reservations and related event flows.

Why build on it

A hotel card is easy. A hotel booking system is not.

Hotel commerce needs supply rules, availability, rates, offers, policies, checkout, payment, confirmation, attribution and reporting. Build on those layers instead of rebuilding them.

Build it yourself

  • Rebuild supply, rate and policy rules
  • Wire checkout to hotel-specific data
  • Stitch attribution across sessions
  • Own payments, refunds and reconciliation
  • Guardrail AI so it can't invent availability
  • Maintain it all as hotels change daily

Build on Wink

  • Integrate hotel-approved supply from Extranet
  • Booking Engine handles checkout, payment and confirmation
  • 6-month attribution preserved per click
  • Subscribe to 64+ webhook events
  • Structured AI handoff via MCP + Agentic AI
  • 5.5% all-in — Booking Engine under every handoff

The model

From first call to confirmed booking.

One integration path from connection to fulfillment.

  1. 1

    Connect

    Add the hosted MCP server or request API access with OAuth2 to start against live contracts.

  2. 2

    Read live contracts

    Search operations and read current request and response schemas — no guessing, no stale docs.

  3. 3

    Build the flow

    Wire search, availability, booking, payment and reporting into your product.

  4. 4

    Subscribe to events

    React to 64+ webhook events: booking status, payments, refunds, cancellations and channel changes.

  5. 5

    Fulfil in Booking Engine

    Every call resolves into Booking Engine for hotel-specific checkout, payment and confirmation.

For AI agents — start here

Connect, then read the live contracts.

A hosted MCP server lets an agent discover Wink’s APIs and build a working integration without guessing at endpoints.

1 · Connect the MCP server

Streamable HTTP endpoint (SSE fallback at /sse). From Claude Code:

claude mcp add —transport http 

wink-docs https://docs.mcp.wink.travel/mcp

Also works with Codex, Cursor and VS Code — see the MCP docs.

2 · Search the live API

Two tools resolve intent to real operations and concept docs:

  • api_searchfind the operation to call — e.g. “lookup inventory”, “create booking”, “payment receipt”
  • docs_searchfind concepts — “authentication”, “webhooks”, “attribution”

Each result returns a wink:// URI — open the operation, its request/response schema, or its task recipe.

3 · Build with the AI Skill

wink-api-builder uses the MCP server as source of truth: api_search → live contracts → auth → verified code, and flags any mismatch with the current API.

Works with Claude Code, Codex and Cursor — see AI Skills.

4 · Hand off to Booking Engine

Create the booking via the API and Booking Engine fulfills it — checkout, payment, confirmation and booking sync to the connected PMS or channel manager, with source context preserved.

Subscribe to booking.created and 63 other events to react in real time.

One engine, every integration

Every integration converges on Booking Engine.

However your product sends demand — API, agent, component or link — the booking resolves in one place you control.

  • REST API
  • MCP / agents
  • Web Components
  • WinkLinks
  • Studio + network
  • Partner apps

Booking Engine

checkout · payment · confirmation

Confirmed booking

Payment taken, guest confirmed, attribution and source context preserved.

Pick your surface

Choose the right surface before you build too much.

From a full custom integration to a lower-lift embedded route.

API & MCP

Build search, booking, payment, webhook, attribution and reporting workflows over REST + OAuth2 — with the MCP server for live contracts.

Explore

Agentic AI

Let AI agents search, book and pay against live hotel supply — completing the booking, not just routing users to a website.

Explore

Booking Engine

Loads hotel-specific data and handles checkout, payment, confirmation and booking completion.

Explore

Web Components

Add bookable cards, maps, grids, buttons and hotel modules to a website or product surface.

Explore

WinkLinks

Publish curated hotel entries under one mobile-first public link.

Explore

Studio + network

Manage partner access, sales channels and attribution context for partner-led demand.

Explore

The full range

From a full API build to a drop-in component.

Go as deep as a full REST + MCP integration — or, when that’s more than the job needs, drop in a Studio Web Component: hotel cards, maps, grids and booking modules. Either way, Booking Engine fulfills the booking underneath.

  • Full REST + OAuth2 API, hosted MCP server and SDKs
  • Or bookable Web Components — cards, maps and grids
  • 64+ webhook events for real-time reconciliation
  • Booking Engine fulfillment underneath every surface
See the Build on Wink docs
A Wink embeddable hotel card Web Component

Developer FAQs

What technical and product teams ask first.

Is there a separate API access product page?
No. API access is handled through the Builders page and the Build on Wink documentation, not through a standalone marketing product page.
Does API access replace Booking Engine?
No. API access routes demand and integration logic. Booking Engine remains the fulfillment layer for hotel-specific checkout, payment, confirmation and booking completion.
Can AI assistants use Wink?
Yes. A hosted MCP server lets AI agents read the live API contracts so they can search live hotel supply, create bookings and take payment through Booking Engine — completing a booking in one flow, not just routing the user to a website. Any hotel is agent-ready once its profile is live on Wink.
Can I embed hotel cards or maps without a full API integration?
Yes. Studio can create Web Components such as hotel cards, maps, grids and other embedded assets when a lower-lift route is enough — Booking Engine fulfills the booking underneath.
Can hotel groups use developer access?
Yes. Hotel groups and technical operators can use developer access where approved to connect Wink supply, booking and reporting workflows with internal systems.
Where should developers start?
Connect to the MCP server, read the Build on Wink documentation, then request API access when the product use case, technical scope and commercial route are clear.
Is developer access open to everyone?
Developer access should be controlled. Public documentation and the MCP server can support evaluation, but API credentials and production use should match the approved product and commercial context.

Ready to build hotel commerce into your product?

Connect the MCP server, read the docs, choose the right integration surface, and request access when your product is ready to connect approved hotel demand to Booking Engine fulfillment.

See documentationRequest API accessTalk to the platform team