Vendor API 3.0

ONDA Vendor API 3.0 is a RESTful API that connects vendors with the ONDA platform. Vendors push property, room type, and rate plan content along with rates and availability to ONDA, and ONDA delivers bookings from OTA channels back to the vendor.

Using version 1.5?

The existing Vendor API 1.5 remains supported. Use 3.0 for new integrations.

note

Detailed guides and endpoint references are currently available in Korean. English translations are in progress.

Two directions of integration

The first thing to understand in 3.0 is the direction of each API call. A vendor is both a client and a server.

Type	Direction	Path pattern	Vendor's role
HUB API	Vendor → ONDA	/gds/vendor/...	Client — calls the ONDA API
Vendor API	ONDA → Vendor	/bookings etc.	Server — provides endpoints ONDA calls

Channel types

Sales channels are either Plus channels (channel_type=hub) or direct channels (channel_type=cms). For Plus channels ONDA handles the contract, listing, and settlement on the property's behalf; for direct channels the property contracts with the OTA directly and runs the channel itself. Rate and availability sync goes through ONDA either way.

This distinction drives both the channel opening flow and how bookings are confirmed. See Overview for the full comparison.

What changed from 1.5

• Content direction reversed — instead of ONDA pulling content with GET, the vendor now pushes it directly with POST and PATCH.
• Rate plan models introduced — a rate plan is the combination of room type × rate plan model.
• Rate and availability split — rates and business days go to POST .../ari, availability to POST .../ari/avails.
• Channel APIs added — channel discovery, open requests, settings, and mapping are handled through the API.

Content taxonomy

Type	Create	Update
Property	POST /gds/vendor/properties	PATCH /gds/vendor/properties/{vendor_property_id}
Room type	POST .../{vendor_property_id}/roomtypes	PATCH .../roomtypes/{vendor_roomtype_id}
Rate plan model	POST .../{vendor_property_id}/rateplan-models	PATCH .../rateplan-models/{vendor_rateplan_model_id}
Rate plan	POST .../roomtypes/{vendor_roomtype_id}/rateplans	PATCH .../rateplans/{vendor_rateplan_id}

Authentication

Include the issued vendor access token in the Authorization header when calling the HUB API.

GET /gds/vendor/meta HTTP/1.1
Authorization: {vendor_access_token}

Base URL

Environment	URL
Development (alpha)	https://vendor.dapi.tport.dev
Production	Provided by your ONDA contact after the integration agreement

Access tokens are issued by your ONDA contact after the integration agreement.

The Vendor API works the other way around — the vendor verifies the request. Implement token and signature validation for requests coming from ONDA.

Common rules

• Create POST · Update PATCH · Read GET, with 200 OK on success
• PATCH follows RFC 7396 Merge Patch. Omitted fields keep their existing values.
• Request and response bodies are JSON.
• Dates and timestamps use ISO 8601 (e.g. 2026-01-20T15:00:00+09:00).

Getting started

1. Partnership agreement — sign the integration agreement with the ONDA business team
2. Credentials — receive staging and production access tokens and base URLs
3. Review the integration guides — ordered from preparation through channel opening to booking operations
4. Fetch the code catalog — call GET /gds/vendor/meta and build your code mapping table
5. Verify on staging, then switch to production