/tradingview/quotes/technicals

POST /api/tradingview/quotes/technicals

Price: 1 credit

Get technical analysis indicators and ratings for a ticker

How to use it

Get technical analysis for a ticker (EXCHANGE:SYMBOL): summary, moving-averages, and oscillators ratings (strong_buy/buy/neutral/sell/strong_sell with numeric scores), oscillators (RSI, Stochastic, CCI, ADX, Awesome Oscillator, Momentum, MACD), and moving averages (EMA/SMA 10/20/50/100/200, Ichimoku, VWMA, Hull).

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", "NASDAQ:TSLA"; minLength: 1)

Response

• @type string (default: "TradingViewTechnicals")
• symbol string required
• summary_rating string nullable
• summary_value number nullable
• moving_averages_rating string nullable
• moving_averages_value number nullable
• oscillators_rating string nullable
• oscillators_value number nullable
• rsi number nullable
• stoch_k number nullable
• stoch_d number nullable
• cci20 number nullable
• adx number nullable
• awesome_oscillator number nullable
• momentum number nullable
• macd_level number nullable
• macd_signal number nullable
• ema10 number nullable
• sma10 number nullable
• ema20 number nullable
• sma20 number nullable
• ema50 number nullable
• sma50 number nullable
• ema100 number nullable
• sma100 number nullable
• ema200 number nullable
• sma200 number nullable
• ichimoku_base_line number nullable
• vwma number nullable
• hull_ma9 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.