Vendor API 3.0 Documentation Released
Documentation for Vendor API 3.0, intended for new integrations, is now available. The existing Vendor API 1.5 remains supported, and you can choose either version from the Vendor API menu at the top.
What Changed from 1.5
Content Delivery Direction Reversed
Previously, ONDA called the vendor API with GET to fetch content. In 3.0, vendors send content directly to ONDA.
- Create:
POST /gds/vendor/properties - Update:
PATCH /gds/vendor/properties/{vendor_property_id}
Retrieval (GET) is kept as a fallback option.
Rate Plan Models Introduced
A rate plan is defined as a combination of room type × rate plan model. Rate plan models are created per property. Each property must have exactly one standalone model, and there is no limit on package models.
Rate and Availability Delivery Separated
- Rates and business days →
POST .../ari(per rate plan) - Availability →
POST .../ari/avails(combined availability per room type)
Both calls carry values common to all channels and per-channel values (channels[]) in a single request.
Channel APIs Added
Channel discovery, opening requests, per-channel settings, and property/room/rate plan mapping are now handled through the API.
Documentation Structure
| Section | Contents |
|---|---|
| Integration guides | 12 chapters, from setup to channel opening, booking operations, and cancellation/refund policy |
| API reference | 38 HUB APIs + 5 vendor APIs = 43 endpoints |
In the HUB API (vendor → ONDA), the vendor is the client. In the vendor API (ONDA → vendor), the vendor is the server. Booking create, confirm, modify, and cancel, as well as cancellation/refund policy lookup, are endpoints the vendor must implement.
AI Development Support
You can download Vendor API 3.0 context files (Claude Code · Cursor · Windsurf) from the AI Tools page.
Notes
- Development (alpha) base URL:
https://vendor.dapi.tport.dev - The production URL and access token are provided by your ONDA contact after the integration contract is signed