![Airbnb Scraper avatar](https://images.apifyusercontent.com/WrswEVKKW54ChNR9A-Q12goWw7ITCSIdoE0RXwKC7ks/rs:fill:92:92/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vR3NOenhFS3pFMnZRNWQ5SE4vQ2xaUm5nTWZxa2NlM1pGd3YtQWlyYm5iX1NjcmFwZXIucG5n.webp)
No credit card required
![Airbnb Scraper](https://images.apifyusercontent.com/WrswEVKKW54ChNR9A-Q12goWw7ITCSIdoE0RXwKC7ks/rs:fill:92:92/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vR3NOenhFS3pFMnZRNWQ5SE4vQ2xaUm5nTWZxa2NlM1pGd3YtQWlyYm5iX1NjcmFwZXIucG5n.webp)
Airbnb Scraper
No credit card required
Scrape cities or direct URLs of Airbnb rentals. Extract descriptions, locations, prices per night, ratings, reviews count, host details, amenities and more. Download scraped data in various formats including HTML, JSON and Excel.
Problem with out of the range (integer) Airbnb ID number in URL
Closed
2024-03-20T08:18:31.997Z WARN Home detail is behind login or no longer available. {"url":"https://www.airbnb.com/rooms/597082611740627300"}
597082611740627300 - is wrong ID, it seems actor has bug on handling integers because actual url on input is - https://www.airbnb.com/rooms/597082611740627363 (where ID is: 597082611740627363 ) .
![zuzka avatar](https://apify-image-uploads-prod.s3.amazonaws.com/Zji7Rt6MKGCn6Ae6A/echDcdqqFXKuFJRiQ-2018-12_%285%29.jpg)
It seems Airbnb changed the length of their IDs and we havent taken in into account. I am not sure though when we will be able to fix that as we have limited capacity at the moment. Have you tried other AIRBNB scrapers in Apify Store?
![lhotanok avatar](https://apify-image-uploads-prod.s3.amazonaws.com/bBQfYX6sapTncJfzo/scPhC8rWcZM6tCBTW-Image_from_iOS.jpg)
Hello, thanks a lot for helping us debugging the issue! It was indeed wrong handling of integers.
The bug should be resolved with the latest build 0.0.63
, see the example run: https://console.apify.com/view/runs/cEdbwM7GNqScR2KDr
FYI, Airbnb started using BigInt
listing IDs while our Actor used a default JSON.parse
method to parse all API responses.
That resulted in saving int
values instead of BigInt
, such as 597082611740627300
instead of 597082611740627363
.
So, a specialized JSON.parse
method was needed to handle BigInt
values properly.
- 178 monthly users
- 34 stars
- 99.4% runs succeeded
- 3.5 days response time
- Created in Dec 2019
- Modified about 8 hours ago