Skip to Content

Changes for page 1. SearchHotelPrices

Last modified by Giorgi Mdivnishvili on 2024/11/06 10:47
From version 15.2
edited by Giorgi Mdivnishvili
on 2024/04/12 18:35
Change comment: There is no comment for this version
To version 17.1
edited by Giorgi Mdivnishvili
on 2024/11/06 10:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -378,7 +378,7 @@
378 378  During the first request, Paging id must be  empty like this  ( "pagingId": "",)  pagenumber is the number of the page, pagerowcount means number of the given result in one page. So in the first request we can search like this:
379 379  
380 380  
381 -==== first request ====
381 +first request
382 382  
383 383  {{code language="Json"}}
384 384   {
... ... @@ -452,6 +452,24 @@
452 452  This documentation outlines the procedural framework for implementing a robust paging and caching strategy within data retrieval systems, detailing parameter usage and operational best practices for both initial and subsequent data fetch operations.
453 453  
454 454  
455 +
456 +== Update ==
457 +
458 +
459 +~1. To identify whether the returned result is from a dynamic or static channel, a field 'isDynamic' has been added to the response. This field can have a value of TRUE or FALSE. Accordingly, if the hotel is from a dynamic channel, the response will show TRUE.
460 +
461 +
462 +{{code language="Json"}}
463 + {
464 + "isDynamic": false
465 + }
466 +
467 + {
468 + "isDynamic": True
469 + }
470 +{{/code}}
471 +
472 +
455 455  == Important ==
456 456  
457 457  {{error}}