<ContactInfo ContactProfileType="PhysicalLocation">
<Addresses>
<Address Language="en-US">
<AddressLine>213 Street Name.</AddressLine>
<CityName>Bangkok</CityName>
<PostalCode>10250</PostalCode>
<CountryName>TH</CountryName>
</Address>
</Addresses>
</ContactInfo>
<ContactInfo ContactProfileType="PhysicalLocation">
<Names>
<Name>
<GivenName>John</GivenName>
<Surname>Smith</Surname>
</Name>
</Names>
<Phones>
<Phone PhoneNumber="+123456789"/>
</Phones>
<Emails>
<Email>admin@test-hotel.com</Email>
</Emails>
</ContactInfo>
There are certain attributes that cannot be updated via content push API.
Some will get an error warning that the value of the attribute cannot be updated while some will just simply be ignored.
Certain chain ID must be added to your API key first in our backend set up to allow property to be created with that chain ID using your API Key.
On our backend set up, each API key has certain property allowance. This error generates only when the allowance is met. Please contact Agoda support to increase the allowance for you.
Onboarding API Certification consists of 2 stages: Self-Certification and Pilot.
Self-Certification: A script testing in survey format for partner to complete after finishing the development. Once the script testing has been validated by Agoda, we will inform partner to move to the next stage.
Self-Certification Link >>> Please click here.
Pilot: Partner starts pushing 2-3 real properties to onboard on Agoda. Once the properties have been auto-enabled by the system with no issue, we will inform partner that they are certified.
End-to-end process is available in production environment only so we suggest you to push a test property to production in Test city. Below are coordinates and details of the Test city.
longitude = 43.331237
latitude = -11.636096
Country code = KM
City name = Test City
It is because the property is flagged as duplication with an existing property on Agoda. Below are the criteria for duplication logic.
Non-chain: Same property name / same location (check lat/long by first 3 decimals)
Chain: same external id within the same chain id
Usually it takes 24-48 hours for a property to live on Agoda by the automated flow given that all required criteria are met.
Images > 3
Main Image
Contract Signed
Once these 3 criteria are met, the automation flow will submit the property to fraud check stage and when it passes fraud check, the property will be activated on Agoda.
Image URL must be whitelisted on Agoda first before images can be processed. Please also note that image URL must be accessible via internet browser.
In case image URL is already whitelisted, it could be server performance issue. Please contact Agoda Support to check on case-by-case basis.
Yes, we recommend 10 minutes wait-time between each creation request when pushing a new property to Agoda.
Property Creation Request
Room Creation Request
Rate Plan Creation Request
Product Creation Request
All images including the existing ones must be included in the property request with OVERLAY or DELTA mode. Images are OVERWRITE by default, therefore, if property would like to add more images, channel manager must include existing images + new images in the request, otherwise, images would be deleted.
Property Route:
Service
Channel
CancelPolicy
ChildAgeBand
Room Route:
AmenityCode
Text Language
RatePlan Route:
ChannelCode
RentalLicense
Direction
HouseRule
LocalRecommendation
Properties will be deleted if they do not go live after 60 days of initial onboarding. In order for property to go live, all required criteria must be met.
Images > 3
Main Image
Contract Signed
Once these 3 criteria are met, the automation flow will submit the property to fraud check stage and when it passes fraud check, the property will be activated on Agoda.
Product is always in overwrite mode so our system would take whatever is the latest push of that particular rate plan.
Therefore, if there's a mistake in product creation, a new request push would correct the mistake by overwriting the existing product.
Product is in OVERWRITE mode by default. Please note that Rate plan is the core of the mapping.
If multiple requests pushed for the same rate plan ID, we will take only the latest (overwrite).
If they are different rate plan IDs, then it will not overwrite.
In case you'd like to link multiple room type ids to one rate plan, we suggest to include multiple room type ids in the same request as per below example.