POST /api/yahoo/finance/options
Price: 10 credits
Get the option chain of a ticker: calls and puts with strike, bid, ask, volume and open interest
Option chain of a stock, ETF or index: calls then puts per expiration date. Pass expiration for one date; without it the chain is walked from the nearest expiration until count is reached.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)symbol string required — Ticker symbol of the underlying (examples: "AAPL", "SPY", "TSLA"; minLength: 1; pattern: \S)expiration integer nullable — Expiration date as unix seconds (UTC midnight of the expiration day); omitted, every listed expiration is returned from the nearest on (examples: 1794960000; min: 0)count integer required — Max number of option contracts (min: 1; max: 5000)@type string (default: "YahooFinanceOption")id string requiredoption_type string requiredunderlying_symbol string requiredstrike number nullablecurrency string nullableexpiration_at integer nullablelast_price number nullablechange number nullablechange_percent number nullablevolume integer nullableopen_interest integer nullablebid number nullableask number nullableimplied_volatility number nullableis_in_the_money boolean nullablecontract_size string nullablelast_trade_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 — Symbol not found or it has no listed options 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.