![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.
WARN Home detail is behind login or no longer available
Closed
i get this log message with the incorrect url. so if i search for https://www.airbnb.com/rooms/896202763378272327.
i get no results whilst i find a log message saying 2024-04-09T13:42:45.983Z WARN Home detail is behind login or no longer available. {"url":"https://www.airbnb.com/rooms/896202763378272400"}
the log message is about a different URL than the one i submitted.
![tri_angle avatar](https://apify-image-uploads-prod.s3.us-east-1.amazonaws.com/c3rq5btz94eFe6Tgm/qSOClRF1iIc8yQBI6-Triangle___Orange_%281%29.png)
Hello Thank you for your message, i will get the developer to look into the issue and get back to you 🔺
giant_crab
OP, try an earlier build, such as 0.0.60. If you go down in the issues log, I reported this a few weeks ago as being a bug in 0.0.61 and 0.0.62. It's the only workaround that I've been able to find.
![lhotanok avatar](https://apify-image-uploads-prod.s3.amazonaws.com/bBQfYX6sapTncJfzo/scPhC8rWcZM6tCBTW-Image_from_iOS.jpg)
Hello, the issue has been fixed, see the example run with the input you provided (build 0.0.63
): https://console.apify.com/view/runs/3ZYjFzjDB0QubmNBY
FYI, our Actor was not handling long listing IDs such as 896202763378272327 correctly (as BigInt
values).
It parsed and stored them as standard integers which caused int overflows. The Actor then crawled URLs with wrong listing IDs.
- 178 monthly users
- 34 stars
- 99.4% runs succeeded
- 3.5 days response time
- Created in Dec 2019
- Modified about 9 hours ago