/yahoo/finance/quotes

POST /api/yahoo/finance/quotes

Price: 1 credit

Get real-time quote for a ticker symbol

How to use it

Get real-time market quote for a stock or crypto ticker. Returns price, change, volume, market cap, exchange, day/52-week range, PE ratios, dividend yield, bid/ask, moving averages, and market open status.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• symbol string required — Ticker symbol (examples: "TSLA", "AAPL", "BTC-USD"; minLength: 1)

Response

• @type string (default: "YahooFinanceQuote")
• id string required
• name string required
• price number required
• change number required
• change_percent number required
• volume integer required
• market_cap integer nullable
• currency string required
• exchange string required
• previous_close number required
• open number required
• day_low number required
• day_high number required
• fifty_two_week_high number nullable
• fifty_two_week_low number nullable
• fifty_day_average number nullable
• two_hundred_day_average number nullable
• average_volume integer nullable
• trailing_pe number nullable
• forward_pe number nullable
• dividend_yield number nullable
• bid number nullable
• ask number nullable
• is_market_open boolean required
• market_time integer nullable

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 — Symbol not found or no quote available 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.