POST /api/yahoo/finance_jp/rankings
Price: 10 credits
List a Yahoo! Finance Japan stock ranking (gainers, losers, volume, trading value, market cap, dividend yield, PER, PBR, company size, margin trading and technical rankings) by market and period: rank, stock code, name, market, last price and the ranked values
Pass a symbol to yahoo/finance_jp/quotes for the full quote.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)ranking string — Ranking (default: "up"; one of: "up", "down", "stopHigh", "stopLow", "yearToDateHigh", "yearToDateLow", "volume", "volumePerUnit", "volumeIncrease", "volumeDecrease", "tradingValueHigh", "tradingValueLow", "marketCapitalHigh", "marketCapitalLow", "shareUnitPriceHigh", "shareUnitPriceLow", "dividendYield", "highPer", "lowPer", "highPbr", "lowPbr", "bbs", "dateOfEstablishment", "listingDate", "cEmployees", "sEmployee", "averageAge", "averageIncome", "amountOfSales", "operatingIncome", "ordinaryProfit", "netIncome", "eps", "totalAssets", "interestBearingDebt", "capital", "roa", "roe", "creditBuybackIncrease", "creditBuybackDecrease", "creditShortfallIncrease", "creditShortfallDecrease", "creditRatioHigh", "creditRatioLow", "highSeparationRate25plus", "highSeparationRate25minus", "highSeparationRate75plus", "highSeparationRate75minus", "lowSeparationRate25plus", "lowSeparationRate25minus", "lowSeparationRate75plus", "lowSeparationRate75minus", "goldenCross", "deadCross")market string — Exchange or market segment (default: "all"; one of: "all", "tokyoAll", "tokyo1", "tokyo2", "tokyoM", "nagoyaAll", "nagoya1", "nagoya2", "nagoyaS", "sapporo", "fukuoka")term string nullable — Ranking period, by default the ranking's own; previous, 5ave and 10ave are the base of the volume-change rankings (one of: "daily", "weekly", "monthly", "previous", "5ave", "10ave")count integer required — Max number of results (min: 1; max: 2500)@type string (default: "FinanceJpRankedStock")ranking_type string requiredrank integer nullablecode string nullablesymbol string nullablename string nullablemarket string nullableurl string nullableprice number nullableprice_date string nullableupdated_at integer nullablevalues array (default: [])@type string (default: "FinanceJpRankingValue")name string requiredvalue number nullabletext string nullable422 — The ranking does not offer that term or market 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 — The entity was not found, or a precondition failed 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.