/yahoo/realestate/realtors

POST /api/yahoo/realestate/realtors

Price: 20 credits

Get a Yahoo! Real Estate Japan (Yahoo!不動産) real-estate company (不動産会社) profile by id or company URL: company name, office address, nearest stations, business hours, license number, holidays, information source and office photos.

How to use it

Fetch a single Yahoo! Real Estate (Yahoo!不動産) real-estate company by id (e.g. '0038553') or a full company URL. Returns name, address, stations (line/station/walk_min), business_hours, license_number, holidays, info_source and images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• realtor string required — Yahoo! Real Estate real-estate company id or a full company URL (examples: "0038553", "https://realestate.yahoo.co.jp/rent/detail_corp/0038553/"; minLength: 1)

Response

• @type string (default: "YahooRealestateRealtor")
• id string required
• url string required
• name string nullable
• address string nullable
• stations array (default: [])
  • @type string (default: "YahooRealestateStation")
  • line string nullable
  • station string nullable
  • walk_min integer nullable
• business_hours string nullable
• license_number string nullable
• holidays string nullable
• info_source string nullable
• images array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Company not found (well-formed id but the company page does not exist) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.