7 days trial then $30.00/month - No credit card required now

VRBO Scraper 2.5

jupri/vrbo-property

Try for free

7 days trial then $30.00/month - No credit card required now

Scrape VRBO.com Properties

Back to issues Create new issue

"Input is not valid: Field input.location is required"

Closed

TheLodges opened this issue

First I want to say thank you so much for keeping this actor up and running. Vrbo has been making so many changes recently and it's a major undertaking to keep tools like this running. Thank you for your hard work. It helps keeps my food on the plate for my family.

Now, for the life of me, I cannot trigger this actor to run via Javascript fetch. I keep getting this "Input is not valid" error. None of the documentation on Apify has helped. Are you able to provide an example of how to pass the location data into this fetch?

let url = "https://api.apify.com/v2/acts/jupri~vrbo-property/run-sync-get-dataset-items?token=apify_api_MY_TOKEN" let headers2 = { 'Method': 'POST', 'Content-Type': 'application/json' }

let response = await fetch(url, {headers}) .then(response => response.json())

Also, it's worth mentioning a bug I found while running this actor while logged into Apify's website. I keep getting an error when I try to run the actor on multiple property IDs. It works perfectly with a single property ID, but it always fails with multiple property IDs, no matter how I sparate them (space, comma, space and a comma, comma and no space, new line, etc... none work).

Thanks again for any help.

cat (Jupri)

Hello @TheLodges, thank You for reaching me out, and thank You for using my actor.

Using JavaScript try this code example:

1const APIFY_TOKEN = "YOUR_APIFY_TOKEN"
2
3var run_inputs  = { "location": "New York" }
4
5var url 		= "https://api.apify.com/v2/acts/jupri~vrbo-property/run-sync-get-dataset-items?token=" + APIFY_TOKEN
6var headers 	= { "content-type": "application/json" }
7var options 	= { method: "POST", headers, body: JSON.stringify(run_inputs) }
8
9var response = await fetch(url, options).then(res => res.json())

Thank You for spotting the problem. Multiple hotel ID should works if you use Expedia-ID. For VRBO-IDs, only support 1 ID. But don't worry, I will fix the problem, so it can support multiple VRBO-IDs, A.S.A.P

TheLodges

Thank you! 1) Your fetch code example is working perfectly for me and 2), I see you fixed the issue with multiple VRBO-IDs. Thank you very much.

I have another question. Should I add it here or create a new issue with each bug/request? (Whichever is better for you)

The question is, are you able to restore the search filter based on minimum number of bedrooms? This was included in an earlier build you created and it's still supported on Vrbo's web UI with the URL query parameter as "bedroom_count_gt". For example:

https://www.vrbo.com/search?adults=2&allowPreAppliedFilters=false&bedroom_count_gt=7&d1=2024-06-01&d2=2024-06-08&destination=Michigan%2C%20United%20States%20of%20America&endDate=2024-06-08&flexibility=0_DAY&latLong=44.314846%2C-85.602364&quick_filter_rooms_spaces_group=&regionId=224&semdtl=&sort=REVIEW_COUNT&sortTriggerPill=&startDate=2024-06-01&theme=&userIntent=

cat (Jupri)

Hey @TheLodges. On last update I have actually fixed the min_bedroom parameter that was previously not working. Its now in Types section. Please check and let me know if you encounter another bugs.