POST /api/yahoo/finance_jp/quotes
Price: 10 credits
Get the quote of a Japanese listed stock from Yahoo! Finance Japan: price and change, the day's open, high, low, volume and trading value, market cap, dividend yield, PER, PBR, EPS, ROE, 52-week range, price limits, the after-hours PTS price and the stock's other listings
Money values are in yen; trading_value and market_cap are whole yen. dividend_yield, roe, equity_ratio and etf_trust_fee are fractions (0.0291 is 2.91%); change_percent is a percent. The etf_* fields are filled for ETFs and pts_* for stocks traded in the evening PTS session.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)symbol string required — Japanese securities code (the Yahoo symbol, 7203.T), with or without the exchange suffix, or a Yahoo! Finance Japan quote URL (examples: "7203", "7203.T", "https://finance.yahoo.co.jp/quote/6758.T")@type string (default: "FinanceJpQuote")code string requiredsymbol string requiredurl string requiredname string nullablemarket string nullablestock_type string nullableindustry string nullableindustry_id string nullableprice number nullablechange number nullablechange_percent number nullableprevious_close number nullableopen number nullablehigh number nullablelow number nullablevolume integer nullabletrading_value number nullablemarket_cap number nullableshares_outstanding integer nullabledividend_yield number nullabledividend_per_share number nullablepe_ratio number nullableeps number nullablepb_ratio number nullablebook_value_per_share number nullableroe number nullableequity_ratio number nullablemin_purchase_amount number nullableround_lot integer nullableyear_high number nullableyear_high_date integer nullableyear_low number nullableyear_low_date integer nullablebid number nullableask number nullableprice_limit_low number nullableprice_limit_high number nullableis_update_stopped boolean nullableis_nisa_growth boolean nullableis_nisa_tsumitate boolean nullableupdated_at integer nullablepts_price number nullablepts_change number nullablepts_change_percent number nullablepts_updated_at integer nullablepts_open number nullablepts_high number nullablepts_low number nullablepts_volume integer nullablepts_trading_value number nullableearnings_release_date integer nullableetf_net_assets number nullableetf_trust_fee number nullableetf_benchmark string nullableetf_management_company string nullableetf_target_assets string nullableetf_target_zone string nullableetf_settlement_frequency integer nullableetf_settlement_month string nullableetf_listing_date integer nullableother_listings array (default: [])@type string (default: "FinanceJpListing")name string nullablesymbol string nullableprice string nullableus_listing object nullable@type string (default: "FinanceJpListing")name string nullablesymbol string nullableprice string nullable422 — 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 — No stock under that code 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.