/tradingview/quotes/financials

POST /api/tradingview/quotes/financials

Price: 1 credit

Get fundamental financials for a ticker

How to use it

Get company fundamentals for a ticker (EXCHANGE:SYMBOL): revenue, gross profit, operating and net income, EBITDA, total assets/debt/equity, free cash flow, EPS, return on equity/assets, margins, debt-to-equity, current and quick ratios, price-to-book, price-to-sales, P/E, and dividend payout ratio. Values are most-recent fiscal year (fy) or trailing-twelve-month (ttm).

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:KO"; minLength: 1)

Response

• @type string (default: "TradingViewFinancials")
• symbol string required
• total_revenue_fy number nullable
• total_revenue_ttm number nullable
• gross_profit_fy number nullable
• oper_income_fy number nullable
• net_income_fy number nullable
• net_income_ttm number nullable
• ebitda_fy number nullable
• total_assets_fy number nullable
• total_debt_fy number nullable
• total_equity_fy number nullable
• free_cash_flow_fy number nullable
• earnings_per_share_basic_fy number nullable
• earnings_per_share_diluted_ttm number nullable
• return_on_equity_fy number nullable
• return_on_assets_fy number nullable
• gross_margin_fy number nullable
• net_margin_fy number nullable
• operating_margin_fy number nullable
• debt_to_equity_fy number nullable
• current_ratio_fy number nullable
• quick_ratio_fy number nullable
• price_book_fq number nullable
• price_sales number nullable
• price_earnings_ttm number nullable
• dividend_payout_ratio_fy 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.