Changes for page 1. SearchHotelPrices
Last modified by Giorgi Mdivnishvili on 2024/11/06 10:47
From version 15.1
edited by Giorgi Mdivnishvili
on 2024/04/11 18:00
on 2024/04/11 18:00
Change comment:
There is no comment for this version
To version 16.1
edited by Giorgi Mdivnishvili
on 2024/11/06 10:45
on 2024/11/06 10:45
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -378,6 +378,17 @@ 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 +{{code language="Json"}} 382 + { 383 + "isDynamic": false 384 + } 385 + 386 + { 387 + "isDynamic": True 388 + } 389 +{{/code}} 390 + 391 + 381 381 ==== first request ==== 382 382 383 383 {{code language="Json"}} ... ... @@ -430,7 +430,6 @@ 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 - 434 434 **Example - Request with Caching**: 435 435 436 436 {{{ { ... ... @@ -453,21 +453,27 @@ 453 453 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. 454 454 455 455 456 -== Important == 457 457 458 -{{error}} 459 -It's Important to in every other request header, put Auth token 467 +== Update == 460 460 461 - **Key**- Authorization469 +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. 462 462 463 -**Value **- Bearer Token what is given in this response. 464 464 472 +== Important == 465 465 466 -**also note in headers that:** 474 +{{error}} 475 +=== Implementing Authorization in Subsequent Requests === 467 467 468 - Content-Type-application/json477 +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: 469 469 470 -**Key - **X-nugios-timezone 479 +* **Header Key:** Authorization 480 +* **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. 471 471 472 -**Value **- 240 482 +Additionally, to ensure your requests are properly formatted and recognized, include the following headers: 483 + 484 +* **Content-Type:** Specify this header as application/json to indicate the format of the request body. 485 +* **Header Key:** X-nugios-timezone 486 +* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes. 487 + 488 +Incorporating these headers with their respective values is essential for the successful processing of your API requests. 473 473 {{/error}}