Turkey has two major property portals worth pulling data from, and they are not interchangeable. Hepsiemlak is the cleaner listings-and-pricing source. Emlakjet carries the analytical extras: price history, demographics, and new-construction projects.
If you are covering the Turkish market, the useful question is which one answers your question, or whether you need both.
Why Turkish property data is its own problem
Three things make Turkey different from most European markets.
Inflation. Turkish property prices have moved at rates that make nominal time series hard to read. A 40% year-on-year rise in asking price is not necessarily a real gain. Any trend analysis needs deflating or converting, and any cached price is stale faster than you expect.
Currency. Listings are quoted in lira, but a meaningful share of demand, particularly in Istanbul and the coastal markets, is foreign and thinks in dollars or euros. The same listing tells a different story depending on the denominator.
Administrative structure. Turkey is organised as 81 provinces (il), subdivided into districts (ilçe), then neighbourhoods (mahalle). Both APIs expose this hierarchy, and you should use it rather than free-text location matching. Turkish place names have suffixes that change with grammatical case, so string matching fails in ways that are hard to debug.
Hepsiemlak: listings and the price index
The Hepsiemlak Turkey API covers 11 endpoints and is the more focused of the two.
Search. /search-property filters across the country by location, price, room count, size and type. /search-by-url takes a Hepsiemlak search URL and returns the same results as JSON, which is the fastest way to turn an analyst’s browser query into a feed. /search-filters returns the valid filter values so you are not guessing.
Detail. /property-details and /property-details-by-url, with /similar-properties for comparables.
Geography. /cities, /counties, /districts and /locations-autocomplete give you the full administrative tree. Resolve to IDs here first.
/price-index. The endpoint that earns its place. A market price index by area, which is exactly what the raw listings cannot give you: a normalised view of where prices sit rather than what one seller is asking. In a high-inflation market this is the difference between an analysis and a number.
Emlakjet: depth and context
The Emlakjet Turkey API runs to 18 endpoints and covers more ground.
The same core, with /search-property, /search-by-url, /property-details, /similar-listings and the full location tree down to /neighborhoods.
/price-history. Price changes on a specific listing over time. Reductions are a genuine signal, both of seller motivation and of where the market is turning. Most portals do not expose this at all.
/nearby-places. What surrounds a property: schools, transport, hospitals, shopping. In Istanbul in particular, metro proximity is one of the strongest price determinants there is.
/area-demographics. Population and demographic characteristics by area. Rare in portal APIs and useful for anything from investment screening to retail site selection.
Agencies. /agents-autocomplete and /agency-listings cover who holds which inventory.
New construction. /project-search and /project-details cover development projects. This matters more in Turkey than in most markets: new-build supply is a large share of transactions, sold on staged payment plans that make it a distinct product from resale.
Choosing
| You need | Use |
|---|---|
| Clean listings plus a market index | Hepsiemlak |
| Price change history on listings | Emlakjet |
| Demographics or nearby amenities | Emlakjet |
| New-construction project data | Emlakjet |
| Agency and inventory intelligence | Emlakjet |
| Cross-checking coverage in one city | Both |
For a straightforward search product, Hepsiemlak plus /price-index is enough. For investment analytics, Emlakjet’s history and demographics carry more of the load. Running both is a reasonable coverage strategy in Istanbul, Ankara and İzmir, where inventory overlaps only partially.
What people build
Search portals for domestic and foreign buyers, where the foreign segment needs currency conversion at the presentation layer, not the data layer.
Investment screening. Combine district price levels with demographics and transport proximity to rank areas, then use price history to spot where asking prices are softening.
Market monitoring. Sample the price index on a schedule and pair it with listing volume. In an inflationary market, volume often turns before price does.
Developer and project tracking. New-build supply by district, with pricing and delivery timelines.
Relocation and expat tools. Neighbourhood data with amenities and transport for people who do not know the city.
Practical notes
Store the currency and the date with every price. This sounds obvious and is the single most common mistake in Turkish market analysis.
Use the administrative hierarchy as your join key rather than place names. Handle both İ and I correctly - Turkish dotted and dotless i are distinct letters, and a naive toLowerCase() in most languages will mangle them.
Treat listings as asking prices. Registered transaction data is a separate source.
Related APIs
For the wider region, see the Aqar Saudi Arabia API or the UAE Real Estate API. The Turkey real estate data guide covers the market page, and the Real Estate Data hub lists every market we carry.
Disclaimer
Happy Endpoint is not affiliated with, endorsed by, or sponsored by Hepsiemlak or Emlakjet. All data is collected from publicly available sources.
