Error message: “API key is not authorized for this property”​

Solution: Submit a request to Agoda Accommodation Services Team (agoda.chain.support@agoda.com) to grant access for channel manager or property can select channel manager in YCS themselves

How to select a channel manager in YCS?

1. Log onto the YCS Extranet

2. Go to ‘Property Settings’ under 'Property' menu 

3. Select 'enable channel manager mode'

4. Select channel manager name from drop-down list, then save

Error message: “Property ID does not exist in Agoda”​

Solution: Property must recheck Agoda property ID again. If property doesn't know their Agoda Property ID, they can reach out to our support team via YCS Help Widget for further support

How to submit a request via Help Widget in YCS?

1. Log onto the YCS Extranet

2. Click on ‘Need Help’ at the bottom right corner

3. Follow the navigation in Partner Support Center

Error message: price update are missing from the request

Solution: Channel manager must recheck the correctness of XML request to always include price update when there's <prices>,</prices> in the XML request. If channel manager would like to update restrictions only, then please remove <prices>,</prices> altogether.

Error message: single price cannot be higher than double rate price

Solution: single rate must be lower or the same price as double rate.

Error message: double rate price cannot be higher than full rate price

Solution: double rate must be lower or the same price as full rate.

Error message: Max LOS value in XML request is not supported by Agoda

Solution: Please recheck Max LOS value in the XML request. Agoda only supports max LOS value between 0 - 99.

Error message: Min LOS value in XML request is not supported by Agoda

Solution: Please recheck Min LOS value in the XML request. Agoda only supports value between 1 - 99.

Error message: Price attributes are missing from the request with OVERWRITE or OVERLAY mode.

Solution: Channel manager must recheck the correctness of XML request to always include price update when there's <prices>,</prices> in the XML request. If channel manager would like to update restrictions only, then please remove <prices>,</prices> altogether.

Error message: “Price update currency does not match currency set up in YCS”​

Solution: Channel manager can submit a request to Agoda Accommodation Services Team (agoda.chain.support@agoda.com) to update currency in YCS on behalf of the property or property can submit a request via Help Widget in YCS

How to submit a request via Help Widget in YCS?

1. Log onto the YCS Extranet

2. Click on ‘Need Help’ at the bottom right corner

3. Follow the navigation in Partner Support Center

Error message: “Updates sent to room type which doesn’t exist or is inactive”

Solution: Property must reactivate roomtype or remove the room from their system before setting updates to it

How to reactivate room types in YCS?

1. Log onto the YCS Extranet

2. Go to ‘Room Setup’

3. Select room to activate by selecting from the checkbox

4. click 'Activate'

Error message: “Max Occupancy set up in YCS is less than price occupancy in the XML request”​

Solution: Property must align occupancy set up between YCS and channel manager​

How to update occupancy set up in YCS?

1. Log onto the YCS Extranet

2. Go to ‘Room Setup’

3. Select room to update occupancy

4. Select the occupacy number from the drop-down, then save

Error message: “Updates sent has extra bed price but extra bed is not set for the room type in YCS”

Solution: Property must set extra bed in YCS for the room type

How to update extra bed for room types in YCS?

1. Log onto the YCS Extranet

2. Go to ‘Room Setup’

3. Select room to update extra bed

4. Go to 'Number of extra beds'

5. Select the extra bed number from drop-down, then save

Error message: “Updates sent to rate plan which doesn’t exist or is inactive”

Solution: Property must reactivate rate plan or remove the it from their system before setting updates

How to reactivate rate plans in YCS?

1. Log onto the YCS Extranet

2. Go to ‘Rate Plan Setup’

3. Select rate plan to activate by selecting from the checkbox

4. click 'Activate'

Error message: “rate plan is a child rate plan and rate update is not allowed”

Solution: Property must unlink child rate plan from a master rate plan or unmap the child rate plan from channel manager

How to unlink a child rate plan?

1. Log onto the YCS Extranet

2. Go to ‘Rate Plan Setup’

3. Select rateplan to unlink from 'Use prices from' (as per an example below)

4. Unselect master rate plan by select 'select a rate plan' from the drop-down menu, then click save

Error message: “Price update in XML request are for dates beyond arrival date range set up in YCS”

Solution: Property must update arrival dates in YCS to cover dates pushed in the request

How to update arrival date in YCS?

1. Log onto the YCS Extranet

2. Go to ‘Rate Plan Setup’

3. Select rateplan to update arrival dates

4. 'To' date can be specified until certain date, or it can also be extended indefinitely, then save

Error message: Requested 'from' date (date_range) in XML request more than 1 day in the past.

Solution: To support western timezone, Agoda allows update only today-1. Please recheck XML request and retry again.

For example, below SetAri request was pushed to Agoda on 2023-08-28, however, the date requested was -2 days. Our system only allows -1 day 

Error message: Requested date_values in XML request is more than 1 day in the past.

Solution: To support western timezone, Agoda allows update only today-1. Please recheck XML request and retry again.

For example, below SetAri request was pushed to Agoda on 2023-08-17, however, the date requested was for June 2023. Our system only allows -1 day 

Error message: duplicate items in inventory updates. There's an overlapping conditions in the same request (room type ID + date)

Solution: Please revise XML request to make sure theres no overlapping conditions of inventory update.

Below is an example of XML request that received this error. The request contains duplicate updates of the same room type ID with overlapping stay dates.

The reason for this validation is to prevent different values for the same conditions being updated in our system.

Error message: duplicate items in rate updates. There's an overlapping conditions in the same request (room type ID/rate plan ID + date)

Solution: Please revise XML request to make sure theres no overlapping conditions of rate update.

Below is an example of XML request that received this error. The request contains duplicate updates of the same room type ID/rate plan ID with overlapping stay dates but with different price value.

The reason for this validation is to prevent different values for the same conditions being updated in our system.

Error message: Requested date in SetARI request is greater than 730 days (from today)

Solution: Agoda only allows updates 730 days in advance. Please kindly implement a validation to send updates not more than 730 days in advance.

For example, below request was pushed on 2023-08-01 but for date range 2025-08-01 which is 731 days in advance.

Error message: Max Advance Purchase value in the XML request is lower than Min Advance Purchase Value.

Solution: Please kindly recheck XML request and adjust min/max advance purchase value accordingly.

Error message: In deviation mode, all deviation occupancy up to max occ set up in YCS is required, but missing in the request.

Solution: Please ensure all occupancy deviation is included in the request. If occupancy set up between channel manager and YCS are not aligned, please kindly update them accordingly.

For example, below room type has max occupancy set up = 3, however, channel manager only pushed deviation price for occupancy 1 and 2 only, missing 3.

Error message: 'from' date is later than 'to' date in the request. 

Solution: Please recheck XML request and repush again.

Error message: Requested 'from' date (date_range) in XML request is more than 1 day in the past.

Solution: To support western timezone, Agoda allows update only today-1. Please recheck XML request and retry again.

For example, below SetAri request was pushed to Agoda on 2023-07-17, however, the date requested was -2 days. Our system only allows -1 day 

Error message: Requested date_values in XML request is more than 1 day in the past.

Solution: To support western timezone, Agoda allows update only today-1. Please recheck XML request and retry again.

For example, below SetAri request was pushed to Agoda on 2023-07-17, however, the date requested was -2 days. Our system only allows -1 day 

Error message: Requested date in SetARI request is greater than 730 days (from today)

Solution: Agoda only allows updates 730 days in advance. Please kindly implement a validation to send updates not more than 730 days in advance.

For example, below request was pushed on 2023-08-22 but has date range until 2025-09-02 which is beyond 730 days in advance from pushed date.

Error message: Mode is missing from SetARIV2 request.

Solution: SetAriV2 (type = 10) required either 'normal' or 'deviation' mode in XML request. Please kindly recheck XML request and retry again.

SetAriV2 Specification can be found here.

Below is an example of SetAriV2 request without the required mode.

Error message: Max LOS value cannot be equal to or less than existing Min LOS value in Agoda system or in the same XML request

Solution: Please recheck min/max LOS value and repush again

Error message: Base price pushed in SetAriV2 request (deviation mode) is outside min/max rate set up at country level on Agoda

Solution: Please recheck XML request

Error message: “Incorrect date input 'from' date is later than 'to' date"

Solution: Channel manager must revise 'from' and 'to' date in the request. 'To' date must be later, not before 'from' date

Example of incorrect request

Error message: Requested 'from' date in GetARI request is greater than 730 days (from today) or is more than 1 day in the past.

Solution: Agoda only allows updates 730 days in advance and -1 day from today, thus date retrieval must be between -1 from today until 730 days in advance only.

For example, below GetAriV2 request was queried on 2023-08-27 but requested for date range from="2025-09-15" to="2025-10-15" which is more than 730 days in advance.

*1102 and 1103 usually returns in the same response.

Error message: Requested 'to' date in GetARI request is greater than 730 days (from today) or is more than 1 day in the past.

Solution: Agoda only allows updates 730 days in advance and -1 day from today, thus date retrieval must be between -1 from today until 730 days in advance only.

For example, below GetAriV2 request was queried on 2023-08-13 but requested for date range from="2023-08-11" to="2023-08-11" which is more than 1 day in the past.

*1102 and 1103 usually returns in the same response.

Error message: “API key is not authorized for this property”​

Solution: Submit a request to Agoda Accommodation Services Team (agoda.chain.support@agoda.com) to grant access for channel manager or property can select channel manager in YCS themselves

How to select a channel manager in YCS?

1. Log onto the YCS Extranet

2. Go to ‘Property Settings’ under 'Property' menu 

3. Select 'enable channel manager mode'

4. Select channel manager name from drop-down list, then save

Error message: “Property ID does not exist in Agoda”​

Solution: Property must recheck Agoda property ID again. If property doesn't know their Agoda Property ID, they can reach out to our support team via YCS Help Widget for further support

How to submit a request via Help Widget in YCS?

1. Log onto the YCS Extranet

2. Click on ‘Need Help’ at the bottom right corner

3. Follow the navigation in Partner Support Center

Error message: property count in GetAri request is more than 5 properties

Solution: GetAriV1 and GetAriV2 can be used to retrieved ARI for not more than 5 properties in a single request. Please revise the request and retry again.

Below is an example of a request that receieved this error. Although property id is the same but the count is over 5.

Error message: GetAri requested dates are more than 31 stay dates.

Solution: Please limit GetAri request to retrieve not more than 31 stay dates in a single request. If channel manager would like to query ARI for more than 31 days, please breakdown queries into multiple GetAri requests but for stay date not more than 730 days in advance.

Below is an example of GetAri request with date criteria more than 31 day count.

Error message: “GetAri request for room type ID which doesn’t exist or is inactive”

Solution: Property must reactivate roomtype or remove the room from their system before sending updates to it

How to reactivate room types in YCS?

1. Log onto the YCS Extranet

2. Go to ‘Room Setup’

3. Select room to activate by selecting from the checkbox

4. click 'Activate'

Error message: “GetAri request for rate plan ID which doesn’t exist or is inactive”

Solution: Property must reactivate rate plan or remove the it from their system before sending updates

How to reactivate rate plans in YCS?

1. Log onto the YCS Extranet

2. Go to ‘Rate Plan Setup’

3. Select rate plan to activate by selecting from the checkbox

4. click 'Activate'

Error message: “Incorrect date input 'from' date is later than 'to' date"

Solution: Channel manager must revise 'from' and 'to' date in the request. 'To' date must be later, not before 'from' date

Example of incorrect request

Error message: “API key is not authorized for this property”​

Solution: Submit a request to Agoda Accommodation Services Team (agoda.chain.support@agoda.com) to grant access for channel manager or property can select channel manager in YCS themselves

How to select a channel manager in YCS?

1. Log onto the YCS Extranet

2. Go to ‘Property Settings’ under 'Property' menu 

3. Select 'enable channel manager mode'

4. Select channel manager name from drop-down list, then save

Error message: Requested dates in GetBookingListV1 is older than 740 days in the past

Solution: Please limit GetBookingList date/time criteria not more than 740 days in the past.

Below is an example of GetBookingListV1 request with date/time criteria over 740 days from queried date (2023-07-27)

Error message: GetBookingList requested date range are more than 90 days.

Solution: Please limit GetBookingList request to retrieve bookings not more than 90 days in a single request. If channel manager would like to retreive bookings for more than 90 days, please breakdown queries into multiple GetBookingList requests but for date range not older than 740 days in the past.

Below is an example of GetBookingListV1 request with date criteria more than 90 day count.

Error message: time zone of 'from' and 'to' date range are different.

Solution: Please recheck GetBookingListV1 request again and retry with the same time zone for both 'from' and 'to' date range.

Below is an example of GetBookingListV1 request with different time zone  in 'from' and 'to' date.

Error message: Requested dates in GetBookingListV2 is older than 740 days in the past

Solution: Please limit GetBookingListV2 date/time criteria not more than 740 days in the past.

Below is an example of GetBookingListV2 request with date/time criteria over 740 days from queried date (2023-08-21)

Error message: Requested time range in GetBookingListV2 is more than 60 minutes

Solution: Please limit GetBookingListV2 date/time range criteria not more than 60 minutes in a single request

Below is an example of GetBookingListV2 request with date/time criteria over 60 minutes (60 minutes and 1 second)