Krisha.kz API

Krisha property search and listing detail

Krisha.kz API returns live Krisha.kz data as clean JSON for krisha.kz The primary endpoint, search, returns listings with source id, canonical URL, title, KZT price and basis, rooms, floor area, city/address, preview, photo, source date text; so….

no credit card1,000 free credits · instant API key · pay by card or crypto
Missing a Krisha.kz endpoint, or need a source we don't have yet?Contact us real people · same-day reply.
K
/krisha/v1

2 active endpoints. Every call is 3 credits.

  • POST/krisha/v1/search
  • POST/krisha/v1/listing

What Krisha.kz endpoints does ReefAPI ship?

2 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.

2 endpoints

search

3 cr

Search public Kazakhstan property sale/rental inventory, preserving source totals and paginat…

required
—
optional
mode, property_type, rent_period, city, rooms, price_min, price_max, area_min, area_max, query, owner_only, has_photo, sort, page

listing

3 cr

Full public listing detail.

required
—
optional
listing_id, url

Every parameter, every allowed value →

Krisha.kz API

2 of 2 endpoints, ready to run

View docs ↗

Find property listings

3 credits0 required · 4 optional
POST/krisha/v1/search
idle
// Press "Try it" and this pane shows exactly what the
// live site returned this second — including an empty
// result, if that is the truth. No key, no account.

How the Krisha.kz API works

Krisha.kz is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.

01
Authenticate
x-api-key header

No OAuth app, no request signing, no per-site account. One key covers all 438 engines.

02
Call
POST /krisha/v1/…

Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.

03
Pay
3 credit per call

Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.

04
Read
{ ok, data, meta, error }

One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.

Search, then resolve the source identity

Use a result from the first call in the second call.

01search(city="almaty", mode="sale", property_type="apartment", page=1)
POSTsearch(city="almaty", mode="sale", property_type="apartment", page=1)

Read the source identity and price.

02listing(listing_id="1014270213")
POSTlisting(listing_id="1014270213")

Replace the example identity with a fresh search result.

Source listing detail with its published price, identity, media and description.

request
curl -X POST https://api.reefapi.com/krisha/v1/search \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"mode":"sale","property_type":"apartment","city":"almaty","page":1}'
response envelope
{
  "ok": true,
  "data": { … },
  "meta": {
    "api": "krisha",
    "endpoint": "search",
    "mode": "live",
    "latency_ms": …,
    "record_count": …
  },
  "error": null
}

Coverage and limits

Measured on 2026-10-02. Core release-ready within documented coverage; not deployed.

Production status

Core release-ready: two distinct fresh cohorts passed search and listing detail.

Market

Kazakhstan. Almaty and Astana were checked in separate fresh cohorts.

Observed groups

Apartment sales/monthly rent, house sales and commercial sales. Other supported source groups have historical evidence, not current release qualification.

Prices

KZT; source sale/rental basis is retained without annualizing rents or concatenating per-square-metre prices.

Detail content

Published media, attributes and descriptions when present. Floor-plan listings can have no prose; starting-price qualifiers are retained.

Optional limits

Advanced filters, nationwide/deep coverage, exact publication dates and map precision are unqualified. Source titles and labels may be Russian or Kazakh.

What people build with Krisha.kz

The jobs this data is most often used for.

2

endpoints

3

credits per call

01

Real-estate investors use Krisha.kz to search public Kazakhstan property sale/rental inventory, preserving source totals and paginat….

02

Brokerage tools use Krisha.kz to get full public listing detail; supply listing_id or url returned by search..

03

Property dashboards use Krisha.kz to compare listings, property details, prices, locations and market inventory, all from one ReefAPI key and credit pool.

What Krisha.kz data costs

The cheapest call here is 3 credits, so $15/mo (Pro) buys 3,333 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.

Full pricing →
$0.67–$1.50 / 1,000 credits
  • 1,000 free credits on signup, no card
  • One key, all 438 APIs, one credit pool
  • Failed and blocked calls are never charged
  • Credits roll over and never expire

Call it in two lines

Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.

curl
curl -X POST https://api.reefapi.com/krisha/v1/search \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"mode":"sale","property_type":"apartment","city":"almaty","page":1}'
python
import requests

r = requests.post(
    "https://api.reefapi.com/krisha/v1/search",
    headers={"x-api-key": REEF_KEY},
    json={
  "mode": "sale",
  "property_type": "apartment",
  "city": "almaty",
  "page": 1
},
)
print(r.json()["data"])
FAQ

Have a question? We got answers.

The questions people actually ask before wiring up Krisha.kz.

Get a free key →
What is the Krisha.kz API?▾

Krisha.kz API is a ReefAPI endpoint group for krisha.kz It returns live JSON through POST requests under /krisha/v1.

Is the Krisha.kz API free to try?▾

Yes. ReefAPI starts with 1,000 free credits, no card required. Krisha.kz calls use the same shared credit balance as every other ReefAPI engine.

Do I need a Krisha.kz login or account?▾

No login to Krisha.kz is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

How fresh is the Krisha.kz data?▾

The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.

How many credits does the Krisha.kz API use?▾

Krisha.kz actions currently cost 3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.

Can I call Krisha.kz from an AI assistant or MCP client?▾

Yes. Connect ReefAPI once through MCP and your assistant can call krisha actions with the same key, credit pool and JSON envelope used by normal REST requests.

Is the Krisha.kz API a Krisha.kz scraper?▾

It is the managed alternative to a DIY Krisha.kz scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same krisha.kz back as clean JSON.

Why does my Krisha.kz scraper keep getting blocked?▾

Most Krisha.kz scrapers break on anti-bot defenses, rate limits and IP bans that need rotating residential proxies and browser fingerprinting to clear. ReefAPI handles all of that for you — no proxies, no captchas, no maintenance — and returns live JSON. Blocked calls are free.

21 Real Estate APIs on the same key

One key, one credit pool, one response envelope. If you are pulling Krisha.kz, you are one call away from the rest of the category — no second contract, no second integration.

Already paying for something else?Krisha.kz vs Bright Data

Need something this API does not do?

Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.

0/4000

No account needed · we reply from [email protected]

Try it on your own data before you pay anything

The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 437 APIs, and the same envelope everywhere.

Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-10-02.