POST /api/google/finance/quotes
Price: 1 credit
Get a real-time quote and company profile for a ticker in SYMBOL:EXCHANGE form
Get the current market quote and company profile for a ticker, identified as SYMBOL:EXCHANGE (e.g. GOOGL:NASDAQ). Returns price, change, day and 52-week range, market cap, volume, PE ratio, dividend yield, shares outstanding, plus profile fields like description, CEO, employees, founding year, headquarters, website, and next earnings date.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)ticker string required — Ticker in SYMBOL:EXCHANGE form (examples: "GOOGL:NASDAQ", "AAPL:NASDAQ", "TSLA:NASDAQ"; pattern: ^[A-Za-z0-9.\-]{1,15}:[A-Za-z0-9.\-]{1,15}$)@type string (default: "GoogleFinanceQuote")id string requiredsymbol string requiredexchange string requiredname string requiredprice number requiredchange number nullablechange_percent number nullableprevious_close number nullableday_high number nullableday_low number nullablefifty_two_week_high number nullablefifty_two_week_low number nullablemarket_cap number nullablevolume integer nullableaverage_volume integer nullablepe_ratio number nullabledividend_yield number nullableshares_outstanding integer nullablecurrency string nullablecountry string nullableindustry string nullabledescription string nullableceo string nullableemployees integer nullablefounded_year integer nullableheadquarters string nullablewebsite string nullablenext_earnings_date string nullableimage 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 — Ticker not found 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.