The search_id parameter has already deprecated. You can simply ignore it and use only the “offset” parameter to load the next page. The items per response is fixed at 20 records.
Please send along with your request so I can reproduce it. Otherwise, I can’t help. In addition, you should recheck required parameters, you may miss it.
Hello,
The search_id parameter has already deprecated. You can simply ignore it and use only the “offset” parameter to load the next page. The items per response is fixed at 20 records.
Regards.
Hello,
It seems like the official developer of Booking did change something to the official system. I will forward your issue to the IT team for review.
Regards.
Sure! Thanks.
This is the entire request:
Please send along with your request so I can reproduce it. Otherwise, I can’t help. In addition, you should recheck required parameters, you may miss it.
Regards.
Thanks!
I’m using RestSharp, I tested the endpont : “properties/list”
i.e.:
var request = new RestRequest(“properties/list”, Method.Get);
request.AddHeader(“X-RapidAPI-Key”, XRapidAPIKey);
request.AddHeader(“X-RapidAPI-Host”, XRapidAPIHost);
RestResponse response = client.Execute(request);
The first init call always returns the right search_id to use with next queries with offset.