Using the API vs collecting it yourself
If you need short-term rental data for the Gulf and Egypt, you can build your own collection or use ours. Here is the trade-off.
Side by side
| JokerPrice API | Collecting it yourself | |
|---|---|---|
| Getting started | Create a key and call an endpoint. | Build and maintain a collector for each platform, plus storage and scheduling. |
| Occupancy | Estimated from daily calendar checks of thousands of tracked listings, with a maturity flag. | Requires checking calendars every day yourself; history starts the day you begin. |
| Normalization | One schema across sources: SAR amounts, ratings out of 10, shared property type ids. | Each platform has its own fields, currencies and rating scales. |
| Breakage | JokerPrice maintains the collectors when platforms change. | Page and API changes on a platform break your collector without notice. |
| Blocking and terms | You call one documented API. | You deal with bot protection, rate limits and each platform's terms yourself. |
| Revenue estimates | POST /api/v1/estimate combines comparables and tracked occupancy, with investment returns. | You design and validate the model. |
| Control | Limited to the destinations, sources and fields JokerPrice collects. | Any field or city you can reach. |
| Cost | Included in the 30-day free trial at 25,000 requests a day for the account, then in every plan, up to 100,000 a day. | Servers, proxies and your time. |
When the API fits
- You need occupancy, ADR or revenue, not only asking prices.
- You want several sources in one schema.
- You would rather spend time on analysis than on collectors.
When building your own fits
- You need a city, platform or field JokerPrice does not collect. Check Data coverage first.
- You need raw page-level detail such as photos, amenities or reviews text, which the API does not return.
- You need history from before JokerPrice started tracking.
Limits to know about
Occupancy is an estimate: a night that closes between two calendar checks counts as booked, so owner blocks can be mistaken for bookings and ADR is the asking price of booked nights, not the achieved rate. Daily history begins when tracking began, so year-over-year comparisons appear after a full year. The method notes explain more.