Skip to main content

Content Creation

This guide describes the values you need to create properties, room types, rate plan models, and rate plans. For the order of steps, see the Initial Setup overview.

Using the code catalog (meta)​

Use ONDA tag codes for fields such as _tags on properties and rooms.

  • GET /gds/vendor/meta returns the available codes.
  • Fetch the list and map your codes to ONDA codes before you create content for the first time.
  • Use the same list to set _tags when you update content.
  • Fetch the list periodically to pick up any codes ONDA adds or removes.

Sending content in languages other than Korean​

To send content in languages other than Korean, add a value for each language to i18n.

  • Applies to the i18n field on properties, room types, rate plan models, and rate plans
  • Choose which language codes to use in your integration. Examples include ko, en, ja, and zh.
  • Match content to each language and choose a fallback for missing translations.
  • Remove characters that cannot be displayed before sending content.

Rate plan model and rate plan structure​

A rate plan links one room type to one rate plan model. The room type and the rate plan model both belong to the property.

:::info Rules for rate plan model type The number of models you can create for a property depends on type.

  • Create exactly one standalone model per property.
  • package: no limit :::

:::tip Channel-specific rate plans — the channels field on a rate plan model To sell a rate plan only on specific channels, set the optional channels field in POST .../rateplan-models.

  • If you omit channels, the rate plan is available on all channels. If you set it, the rate plan is available only on the listed channels.
  • When opening a channel, ONDA creates rate plan mappings for a listed channel only if its room mapping is in place and open.
  • Changes to channels after opening work as follows.
    • Adding ([131] → [131, 132]): a mapping is created for 132 only
    • If you remove channel 132 ([131, 132] → [131]), ONDA keeps existing mappings. Rate plans you create later have no mapping for channel 132.
    • Empty ([131, 132] → []): mappings are created on every eligible channel :::

Property default extra adult charge (settings.extra_adult_price)​

Set the default charge for an additional adult in the settings object when you create or update the property.

  • Value: integer (KRW). Sending null clears it.
  • Legacy channels: included in occupancy-based rates on Agoda and Trip.com. Not included in per-room rates.
  • Plus channels: used as the extra occupancy charge.

Content endpoints​

All paths are prefixed with /gds/vendor.

ObjectMethodPathRequired fields and notes
PropertyPOST/propertiesRequires id and i18n (ko-kr); supports settings.extra_adult_price
PropertyPATCH/properties/{vendor_property_id}Update; clear extra_adult_price with null
PropertyGET/properties · /{vendor_property_id}Fallback lookup
Room typePOST/properties/{vendor_property_id}/roomtypesRequires id and i18n (ko-kr)
Room typePATCH.../roomtypes/{vendor_roomtype_id}Update
Room typeGET.../roomtypes · /{vendor_roomtype_id}Fallback lookup
Rate plan modelPOST/properties/{vendor_property_id}/rateplan-modelsRequires id and i18n (ko-kr); optional channels
Rate plan modelPATCH.../rateplan-models/{vendor_rateplan_model_id}Update
Rate plan modelGET.../rateplan-models · /{vendor_rateplan_model_id}Fallback lookup
Rate planPOST.../roomtypes/{vendor_roomtype_id}/rateplansRequires id and vendor_rateplan_model_id
Rate planPATCH.../rateplans/{vendor_rateplan_id}Update
Rate planGET.../rateplans · /{vendor_rateplan_id}Fallback lookup
warning

When you create a rate plan, set the required vendor_rateplan_model_id field to the ID of its rate plan model.