POST /api/yahoo/finance_jp/forum
Price: 10 credits
List the newest posts of a Japanese listed stock's Yahoo! Finance Japan forum (掲示板): post id, title, text, the poster's sentiment, like and dislike counts, reply target, author and posting time
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")count integer required — Max number of results (min: 1; max: 72)@type string (default: "FinanceJpForumPost")id string requiredsymbol string requiredurl string requiredthread_id string nullablereply_to_id string nullabletitle string nullabletext string nullablesentiment string nullablelike_count integer nullabledislike_count integer nullableimage string nullableauthor_id string nullableauthor_name string nullableauthor_image string nullableposted_at integer 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.