/tradingview/quotes/performance

POST /api/tradingview/quotes/performance

Price: 1 credit

Get price performance and volatility for a ticker

How to use it

Get price performance for a ticker (EXCHANGE:SYMBOL): percent change over 5 days, week, 1/3/6 months, year-to-date, 1/5/10 years, and all time, plus daily/weekly/monthly volatility, all-time high/low, and 52-week high/low.

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 in EXCHANGE:SYMBOL form (examples: "NASDAQ:AAPL", "NYSE:JPM"; minLength: 1)

Response

• @type string (default: "TradingViewPerformance")
• symbol string required
• change number nullable
• perf_5d number nullable
• perf_week number nullable
• perf_1m number nullable
• perf_3m number nullable
• perf_6m number nullable
• perf_ytd number nullable
• perf_year number nullable
• perf_5y number nullable
• perf_10y number nullable
• perf_all number nullable
• volatility_day number nullable
• volatility_week number nullable
• volatility_month number nullable
• all_time_high number nullable
• all_time_low number nullable
• fifty_two_week_high number nullable
• fifty_two_week_low number 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 — 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.

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.