hepsiemlak

Searches real estate in Turkey.

city, listingType, and mainCategory are required — the user must specify which city to search in, whether they are looking for a property for sale or for rent, and the main category of the property.

Location hierarchy (from largest to smallest):

• city (İl): Top level, e.g., İstanbul, Ankara (required)
• county (İlçe): Under city, e.g., Şişli is a county in İstanbul
• district (Mahalle): Under county, e.g., Fulya is a district in Şişli
• area: Specific neighborhoods or landmarks within a county

Use the locationQuery parameter to narrow down to a specific county, district, or area within the city. If no locationQuery is provided, searches the entire city.

Point of Interest (POI) search: When the user references a landmark, park, hospital, venue, address, or "X yakınında / çevresinde" (e.g. "Gülhane Parkı yakınındaki ilanlar", "Galata Kulesi çevresinde", "İstinyePark AVM yanı"): 1. Set required city to the city where the place is located (e.g. İstanbul). 2. Set poiQuery to the place name only as a string (e.g. poiQuery: "Gülhane Parkı", poiQuery: "Galata Kulesi"). 3. Do NOT set latitude, longitude, or locationQuery — the server resolves the coordinates via Google Geocoding. Use locationQuery only for county, district, or area names (e.g. "Şişli", "Kadıköy", "Başakşehir" as ilçe), not for hospitals, parks, or named venues.

Room / Section count fields – important distinction:

• For residential properties (konut / daire / residence type) — when mainCategory is residential:
• bedroomCount: number of bedrooms (yatak odası)
• livingRoomCount: number of living rooms / salons (usually the larger "salon" area)
• isStudio: true = studio apartment (no separate bedroom)

Turkish users very commonly use the "X+Y" notation (salon + yatak odası), e.g.:

• "3+1" → bedroomCount: 3, livingRoomCount: 1
• "2+1" → bedroomCount: 2, livingRoomCount: 1
• "4+2" → bedroomCount: 4, livingRoomCount: 2
• "5+1" → bedroomCount: 5, livingRoomCount: 1

→ Automatically detect and parse this notation when it appears in the user's natural language query and map it to the correct schema fields.

• For commercial properties (işyeri / office / shop / warehouse etc.) — when mainCategory is commercial:
• sectionNumber: number of sections / rooms / compartments (bölüm sayısı)

Commonly used in Turkish commercial listings as "3 bölümlü", "4 odalı ofis", etc. Example mapping: "3 bölümlü" or "3 odalı" → sectionNumber: 3

Summary – which field to use depending on mainCategory:

| mainCategory | Use these fields for room/section count | Turkish example notation | |----------------|------------------------------------------------------|-------------------------------| | Residential | bedroomCount + livingRoomCount (or isStudio) | 3+1, 2+1, 4+2, stüdyo | | Commercial | sectionNumber | 3 bölümlü, 4 odalı |

Recognize and convert this popular notation automatically when the user uses it in their query.

Building age (buildingAge) — mapping guidelines:

buildingAge accepts an array, so multiple age ranges can be sent together to widen the search.

| User intent / phrase | buildingAge value | |------------------------------------------------------------------|--------------------------------| | "sıfır daire", "sıfır ev", "hiç kullanılmamış" | ["New Build"] | | "yeni daire", "yeni yapı", "yeni bina", "az yaşlı bina" | ["New Build", "1-5"] | | "depreme dayanıklı", "sağlam bina", "deprem yönetmeliğine uygun" | ["New Build", "1-5", "6-10"] |

• "Sıfır" (zero / brand-new, never occupied) → only New Build.
• "Yeni daire" or similar phrases implying a relatively new but not necessarily brand-new property → New Build + 1-5.
• Earthquake-safety related phrases ("depreme dayanıklı", "sağlam bina") → New Build + 1-5 + 6-10 (all buildings constructed under modern seismic codes).

The response may include alternative location suggestions if multiple locations match the query.