Get Japan Real Estate data with one API

In yen, already multiplied out, and both transaction types were checked. A Tokyo rental showing price_ja '7.5万円' returned price_jpy 75000, and an Osaka resale showing price_ja '498万円' returned price_jpy 4980000. You never need to multiply by 10,000. The one place man-yen survives is the filter: max_price_man is in man-yen, so 10 caps rent at 100,000 yen a month and 5000 caps a sale at 50 million yen.

Because SUUMO sale pages have no id-only URL to reconstruct. Rentals live at /chintai/jnc_<12-digit id>/ and can be fetched by listing_id alone; sales live at a path that includes the prefecture and the ward, such as /ms/chuko/osaka/sc_osakasayama/nc_20227675/, which cannot be derived from the id. Passing a sale listing_id returned MISSING_PARAM saying exactly that. Copy the `url` from the search result instead and pass it with the matching listing_type.

The recurring costs and the building facts a buyer needs, and they arrive as Japanese strings rather than parsed numbers: management_fee_ja ('8600円／月（委託(通勤)）'), repair_fund_ja ('4130円／月'), total_units_ja ('293戸'), zoning_ja ('２種住居'), handover_ja ('即引渡可') and updated_ja ('2026年8月2日'). Those five are not advertised in the action's declared return shape but were present on the sale listing measured. Budget for the monthly fees separately: on that 4.98 million yen apartment they came to 12,730 yen a month before anything else.

Because the two pages title the same property differently. The search row carried the agent's marketing headline, and the detail page for the same listing carried a generated title of building name, price and layout. property_name_ja is the field that stayed identical across both, so use it as the building's name and treat title_ja as display copy. On rentals the two agree, since a rental row is titled with the building name in both places.

Call `areas`, which returns all 47 with four fields each: a romaji slug, the kanji name, ar and ta. The slug or the kanji both work as the `prefecture` parameter. ar is the SUUMO region grouping, only nine values from 010 to 090, so tokyo and kanagawa share 030 while kyoto and osaka share 060. ta is the JIS prefecture code, unique per prefecture, 01 for hokkaido through 47 for okinawa. Pass `query` to filter, for example 'osa' returned only osaka.

They came back null on all three Tokyo rentals sampled, along with deposit_ja and key_money_ja. SUUMO does not print shikikin and reikin on every listing page, and where the page does not print them there is nothing to parse, so the field is null rather than zero. Read null as unknown, not as 'no deposit required'. admin_fee_jpy is more reliably present on search rows, at 8,000 to 10,000 yen a month on the listings measured.

It varies by listing type. A Tokyo rent page returned 52 items and an Osaka buy_apartment page returned 30, both with max_pages 1, because rentals list every available unit under one building block. has_next_page and next_page tell you whether to continue, and max_pages up to 20 merges pages in a single call, stopping early on an empty page. meta.stop_reason says which limit ended the run.

Each entry has access_ja, the raw Japanese line naming the railway line and station, plus walk_minutes and bus_minutes parsed out of it. Search rows return every line a property is near: one Tokyo rental came back with three entries at 1, 10 and 16 minutes on the Hanzomon, Oedo and Shinjuku lines, each number matching its own access_ja string. The formatting differs slightly between rent and sale pages, so keep access_ja as the source of truth and treat walk_minutes as the sortable convenience field.

Japan Real Estate API is a ReefAPI endpoint group for japan property listings and details. It returns live JSON through POST requests under /japan-re/v1.

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

No login to Japan Real Estate 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.

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

Japan Real Estate actions currently cost 1-2 credits per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.

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