/investing/quotes

POST /api/investing/quotes

Price: 10 credits

Get a market quote for an instrument by alias, section path, or URL

How to use it

Get a real-time market quote for any Investing.com instrument (stock, index, ETF, currency, crypto, commodity, bond) by its alias, section path, or URL. Returns price, day open/high/low, change, previous close, 52-week range, volume, pre-market and after-hours prices, multi-horizon return percentages (1d/1w/1m/3m/6m/ytd/1y/3y/5y/all-time), exchange, currency, and fundamentals (market cap, EPS, P/E, dividend, yield, shares outstanding, beta, next earnings date).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• quote string required — Instrument to look up: a ticker symbol or name ('AAPL', 'Bitcoin'), a section path ('/equities/apple-computer-inc'), or a full instrument URL. Works for stocks, indices, ETFs, currencies, crypto, commodities and bonds. (examples: "AAPL", "/indices/us-spx-500", "https://www.investing.com/crypto/bitcoin"; minLength: 1)

Response

• @type string (default: "InvestingQuote")
• id integer required
• alias string required
• path string required
• symbol string nullable
• name string nullable
• type string nullable
• is_open boolean nullable
• currency string nullable
• exchange string nullable
• exchange_full_name string nullable
• market_name string nullable
• country_flag string nullable
• image string nullable
• last number nullable
• open number nullable
• high number nullable
• low number nullable
• previous_close number nullable
• change number nullable
• change_percent number nullable
• bid number nullable
• ask number nullable
• volume integer nullable
• average_volume integer nullable
• fifty_two_week_high number nullable
• fifty_two_week_low number nullable
• one_year_change number nullable
• premarket_price number nullable
• premarket_change number nullable
• premarket_change_percent number nullable
• after_hours_price number nullable
• after_hours_change number nullable
• after_hours_change_percent number nullable
• extended_hours_session string nullable
• last_update_at integer nullable
• market_cap integer nullable
• eps number nullable
• pe_ratio number nullable
• dividend number nullable
• dividend_yield number nullable
• revenue integer nullable
• shares_outstanding integer nullable
• beta number nullable
• next_earnings_date string nullable
• isin string nullable
• ticker string nullable
• components_count integer nullable
• rank integer nullable
• available_supply number nullable
• max_supply number nullable
• price_usd number nullable
• volume_24h number nullable
• percent_change_7d number nullable
• price_changes object nullable
  • @type string (default: "InvestingPriceChange")
  • one_day number nullable
  • one_week number nullable
  • one_month number nullable
  • three_month number nullable
  • six_month number nullable
  • ytd number nullable
  • one_year number nullable
  • three_year number nullable
  • five_year number nullable
  • all_time number nullable
• technical_summary object nullable
  • @type string (default: "InvestingTechnicalSummary")
  • five_min string nullable
  • fifteen_min string nullable
  • thirty_min string nullable
  • one_hour string nullable
  • five_hour string nullable
  • daily string nullable
  • weekly string nullable
  • monthly string nullable
• url string 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 — Instrument 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.

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.