Plus Channel Opening
How to open a Plus channel (channel_type=hub), where ONDA handles the OTA contract on your behalf. The vendor submits the request to ONDA through the HUB API.
Unlike direct channels, Plus channels have no mapping or authorization step. Once the document prerequisite below is met, they open on the request alone.
The property's license document (permit) and business registration (business) must both be approved (confirm) before a Plus channel can be opened. See Initial Setup — License Submission.
Step by step
- List all channels —
GET /gds/vendor/channels - List channels available for the property —
GET .../properties/{vendor_property_id}/channels - Submit the opening request —
POST .../properties/{vendor_property_id}/channels/{channel_id} - Check the request status —
GET .../properties/{vendor_property_id}/channels/{channel_id}
Checklist
- Review the full channel list and usage notes
- Check which channels the property can open
- Track request status and history after submitting
- Confirm whether rates and availability must be sent before opening completes
- Verify the property and room conditions are met beforehand — requests are auto-rejected otherwise
- Confirm the property's
settings.extra_adult_priceis applied as the extra-occupancy charge on Plus channels
Opening conditions
Opening requests validate the property and room conditions below. A request is automatically rejected if any one of them fails.
Property conditions
| Check | Requirement |
|---|---|
| Duplicate request | Rejected if an open request is sent for a channel that is already ON, or a stop-sale request for one that is already OFF |
| Sales status | Active in both ONDA Hub and the vendor's own system |
| Deleted | Deleted properties are excluded |
| Property name | Rejects invalid values such as null or a single character |
| Images | At least 3 |
| Address | A correct address must be entered |
| Category | At least 1 assigned |
Room conditions
| Check | Requirement |
|---|---|
| Sellable rooms | At least 1 |
| Room name | Rejects invalid values |
| Room images | At least 3 |
| Bookable dates | At least one date within D+0 to D+30 that meets all three conditions: rate, availability, and business day |
How requests are processed
Processing depends on the processing_mode value in the channel metadata.
processing_mode | Behavior |
|---|---|
auto_approve | Activated immediately — request_status: "confirm" |
external_review | Awaits operator approval — request_status: "pending" → confirm or reject |
For external_review channels, poll the request status to find out the result.
Endpoints
All paths are prefixed with /gds/vendor.
| Method | Path | Description |
|---|---|---|
GET | /channels | Channel metadata (channel_type, processing_mode, requires_cms_authorization) |
GET | /properties/{vendor_property_id}/channels | Channels available for the property, with request status |
POST | /properties/{vendor_property_id}/channels/{channel_id} | Submit an ON request (request_type: "on") |
GET | /properties/{vendor_property_id}/channels/{channel_id} | Request status and history |