Content Update

When content changes on the vendor side, push it to ONDA with PATCH. Lookups (GET) exist as a fallback.

Step by step

Checklist

• PATCH only the content that changed
• Confirm the direction is vendor → ONDA (push)
• Push settings.extra_adult_price changes with PATCH .../properties/{vendor_property_id}, sending null to clear it
• Apply the mapping rules when changing channels on a rate plan model
• (Optional) Verify the fallback lookups work

Changing the property's default extra adult charge

settings.extra_adult_price (integer KRW) is changed through the settings object on property update, and sending null clears it. It applies to occupancy-based rates on legacy Agoda and Trip.com, and to extra-occupancy charges on Plus channels.

Mapping changes when editing channels on a rate plan model

• Adding ([131] → [131, 132]): a mapping is created for 132 only
• Removing ([131, 132] → [131]): existing mappings are kept, not deleted. Rate plans created afterwards get no mapping for 132
• Empty ([131, 132] → []): mappings are created on every eligible channel

Endpoints

Pushing changes (required)

Target	Endpoint
Property	PATCH /gds/vendor/properties/{vendor_property_id}
Room type	PATCH .../roomtypes/{vendor_roomtype_id}
Rate plan model	PATCH .../rateplan-models/{vendor_rateplan_model_id}
Rate plan	PATCH .../rateplans/{vendor_rateplan_id}

Fallback lookups (optional)

Target	List	Single
Property	GET /gds/vendor/properties	GET .../{vendor_property_id}
Room type	GET .../roomtypes	GET .../{vendor_roomtype_id}
Rate plan model	GET .../rateplan-models	GET .../{vendor_rateplan_model_id}
Rate plan	GET .../rateplans	GET .../{vendor_rateplan_id}

tip

Content creation and updates flow vendor → ONDA as a push (POST and PATCH) by default. Lookups are an optional fallback; decide whether to implement them based on your operational needs.