Change Log
Changelog
📅 February 2026
Data Type Migration: INT to LONG (64-bit) 🔄
Agoda is migrating high-volume identifiers across core APIs from INT (32-bit) to LONG (64-bit) to support business growth and prevent capacity limits.
Schema changes:
| API | Present in | Field Path | New Type |
|---|---|---|---|
| Search API | Response | properties > rooms > roomId | Long |
| Search API | Response | properties > rooms > parentRoomId | Long |
| Precheck API | Response | errorMessage > priceMismatchData > searchResponse > properties > rooms > roomId | Long |
| Precheck API | Response | errorMessage > priceMismatchData > searchResponse > properties > rooms > parentRoomId | Long |
| Book API | Response | bookingDetails > id | Long |
| Book API | Response | bookingDetails > itineraryID | Long |
| Book API | Response | errorMessage > priceMismatchData > searchResponse > properties > rooms > roomId | Long |
| Book API | Response | errorMessage > priceMismatchData > searchResponse > properties > rooms > parentRoomId | Long |
| Booking Detail API | Request | bookingIds | Long |
| Booking Detail API | Response | bookings > bookingId | Long |
| Booking List API | Response | bookings > id | Long |
| Amendment API | Request | bookingId | Long |
| Amendment API | Response | bookingId | Long |
| Confirm Amendment API | Request | bookingId | Long |
| Confirm Amendment API | Response | bookingId | Long |
| Cancel API | Request | bookingId | Long |
| Cancel API | Response | cancellationSummary > bookingId | Long |
| Confirm Cancel API | Request | bookingId | Long |
| Special Request API | Request | bookingId | Long |
| Content Feed 6 API | Response | roomtypeFeed > roomtypes > roomtypes > hotelRoomtypeId | Long |
| Content Feed 6 API | Response | roomtypeFeed > roomtypes > roomtypes > hotelMasterRoomtypeId | Long |
| Content Feed 19 API | Response | hotelFullFeed > roomtypes > roomtype > hotelRoomtypeId | Long |
| Content Feed 19 API | Response | hotelFullFeed > roomtypes > roomtype > hotelMasterRoomtypeId | Long |
| Content Feed 14 API | Response | roomTypeFacilityFeed > roomTypeFacilities > roomTypeFacility > hotelRoomTypeId | Long |
📅 January 2026
Search 2.0 is now live
Streamlined, context-driven API that lets you use a single site ID integration to access Agoda's offers for any user segment, channel, or country - supporting both live and cached searches.
Benefits:
- Simplified Integration: One site ID covers all user segments - no more multiple integrations
- Greater Flexibility: Fetch offers for any channel, user group, or country with a single API call
- Operational Efficiency: Reduce technical complexity and maintenance
- Enhanced Offer Targeting: Deliver the most relevant offers to your users, boosting conversion
- Future-Proof Platform: Easily supports new channels, user groups
📖 Reference: Search 2.0 API Specification
📅 August 2025
Amendment API is now live
Ability to amend bookings via API for eligible bookings. Supported amendments include date changes, guest name changes, and special requests modifications.
Benefits:
- Cost Saving: Reduce customer service touch points, saving handling time and associated costs
- Improved Customer Experience: Customers can self-serve amendments without contacting support
- Operational Efficiency: Automate amendment workflows with 2 new APIs (Amendment API & Confirm Amendment API)
- Better Booking Management: Track amendment history and check allowed amendments for your bookings
📖 Reference: Amendment API Specification
Fee Waiver Feature is now live
For eligible bookings, request fee waivers for non-refundable bookings. (Please note that the final decision rests with the hotel.)
Benefits:
- Cost Saving: Eliminates unnecessary customer service touch points and handling time for partners
- Streamlined Process: Simplified cancellation flow - only call Confirm Cancel API for fee waiver requests
- Better Customer Retention: Offer customers a path to recover fees on non-refundable bookings
- Reduced Manual Work: Automated fee waiver request delivery eliminates manual procedures
📖 Reference: Fee Waiver API Specification
📅 July 2025
HCN live in Booking Details API
Hotel Confirmation Number is a unique reference number, usually the same as the hotel's own confirmation number. Customers can use this number when contacting the hotel to quickly locate their reservation. We output hotelConfirmationNumber through: BookingDetailResponseV4 -> bookings -> hotelConfirmationNumber
Benefits:
- Easier Customer Communication: Makes it easier for customers to communicate directly with hotels
- Reduced Support Load: Reduces the need for CS support interventions
- Improved Booking Experience: Enhances the overall booking experience with direct hotel reference
📖 Reference: Booking Details API Specification