Skip to main content

Initial Setup

The first sync: the vendor creates property, room type, rate plan model, and rate plan content with POST, submits licenses, then pushes rates and availability (ARI) to make the property sellable. Content always flows vendor → ONDA; content lookups (GET) are a fallback. Check document approval with the submission list or detail lookup.

Step by step​

  1. Fetch the code catalog — GET /gds/vendor/meta (tag codes such as _tags used when creating properties and rooms)
  2. Create the property — POST /gds/vendor/properties
  3. Submit licenses — POST .../{vendor_property_id}/licenses (license document and business registration; both must be approved before opening a Plus channel)
  4. Create room types — POST .../{vendor_property_id}/roomtypes
  5. Create rate plan models — POST .../{vendor_property_id}/rateplan-models
  6. Create rate plans — POST .../roomtypes/{vendor_roomtype_id}/rateplans (bound via vendor_rateplan_model_id)
  7. Push rates and business days — POST .../ari (per rate plan)
  8. Push availability — POST .../ari/avails (consolidated per room type)

Checklist​

  • Fetch the code catalog (_tags and similar) with GET /gds/vendor/meta and build the mapping table into your system
  • Create in order: property → room type → rate plan model → rate plan
  • After creating the property, submit the license document (permit) and business registration (business), and confirm both reach confirm before opening a Plus channel
  • Use tag codes from the meta lookup for _tags when creating properties and rooms
  • Verify the vendor_rateplan_model_id binding when creating rate plans
  • Push rates and business days per rate plan with POST .../ari, and availability per room type with POST .../ari/avails
  • Send the shared value (default) and the full per-channel declaration (channels[]) together in a single call
  • Use partial pushes: include only what changed in ari (business day is_business_day, or rates basic_price, sale_price, net_price)
  • Align ari/avails availability to room-only (room type) counts; each from-to range spans at most 730 days
  • (Optional) Verify the fallback content lookups (GET)

Detailed guides​

StepsGuide
1, 2, 4–6Content Creation — code catalog, languages, rate plan structure, endpoints
3License Submission — document types, file rules, review status, license type codes
7, 8Rates & Availability Push — ARI and Avails examples and rules