Skip to Content

Changes for page 1. SearchHotelPrices

Last modified by Giorgi Mdivnishvili on 2024/11/06 10:47
From version 18.1
edited by Giorgi Mdivnishvili
on 2024/11/06 10:47
Change comment: There is no comment for this version
To version 15.1
edited by Giorgi Mdivnishvili
on 2024/04/11 18:00
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   {
... ... @@ -430,6 +430,7 @@
430 430  ** To navigate through the dataset, adjust the pageNumber while keeping the pagingId constant.
431 431  ** To refresh the dataset and clear the cache, initiate a new request without a pagingId.
432 432  
433 +
433 433  **Example - Request with Caching**:
434 434  
435 435  {{{ {
... ... @@ -452,39 +452,21 @@
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 -
473 473  == Important ==
474 474  
475 475  {{error}}
476 -=== Implementing Authorization in Subsequent Requests ===
459 +It's Important to in every other request header, put Auth token
477 477  
478 -For every API request after the initial authentication, it's crucial to include the authorization token in the request header. This ensures your requests are authorized and can access the necessary resources. Here's how to properly include your token:
461 +**Key **- Authorization
479 479  
480 -* **Header Key:** Authorization
481 -* **Header Value:** Bearer [Your Token Here] - Use the bearer token provided in the initial authentication response. The authorization type should be specified as Bearer Token.
463 +**Value **- Bearer Token what is given in this response.
482 482  
483 -Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
484 484  
485 -* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
486 -* **Header Key:** X-nugios-timezone
487 -* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
466 +**also note in headers that:**
488 488  
489 -Incorporating these headers with their respective values is essential for the successful processing of your API requests.
468 +Content-Type - application/json
469 +
470 +**Key - **X-nugios-timezone
471 +
472 +**Value **- 240
490 490  {{/error}}