Tradingview Authentication

generated: '2026-11-05'
method: searched
source: openapi/tradingview-broker-rest-api-openapi.yml
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - authorizationCode
  - clientCredentials
schemes:
- name: PasswordBearer
  type: http
  scheme: bearer
  bearerFormat: Bearer ACCESS_TOKEN
  description: 'This flow uses login and password to authenticate a user. Username and password are sent as parameters

    to the [/authorize](/rest-api-spec/#operation/authorize) endpoint.


    If the username and password are valid, then the broker issues an access token

    and returns it in the response. The access token is sent with every request in the Authorization header.'
  sources:
  - openapi/tradingview-broker-rest-api-openapi.yml
- name: OAuth2Bearer
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://your-rest-implementation.com/api/authorize
    tokenUrl: https://your-rest-implementation.com/api/oauth/token
    scopes: 1
  description: 'TradingView supports OAuth 2 Authorization Code flow (standard) and OAuth 2 Authorization Code flow with PKCE, as described in
    [RFC 6749](https://tools.ietf.org/html/rfc6749) and [RFC 7636](https://tools.ietf.org/html/rfc7636), respectively.

    After performing authorization, the access token is sent with every request in the `Authorization` header.


    **Code Flow:**


    For OAuth 2 Code Flow the broker p'
  sources:
  - openapi/tradingview-broker-rest-api-openapi.yml
- name: ServerOAuth2Bearer
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://your-rest-implementation.com/api/authorize/token
    scopes: 1
  description: 'This authentication flow is used for server-to-server requests where authentication needs to be done without human intervention.

    It can be used with the [/history](#operation/getHistory), [/symbol_info](#operation/getSymbolInfo), [/streaming](#operation/streaming)

    and [/groups](#operation/getGroups) endpoints.


    JSON Web Token (JWT) is used to securely transmit information between broker and Tradin'
  sources:
  - openapi/tradingview-broker-rest-api-openapi.yml
- name: TradingView MCP OAuth 2.1
  type: oauth2
  surface: https://mcp.tradingview.com/mcp
  description: Authentication is OAuth 2.1 — you log in with your TradingView account, no API keys to manage.
  sources:
  - https://www.tradingview.com/mcp/docs
docs: https://www.tradingview.com/mcp/docs
note: Broker REST API schemes are implemented by the broker (TradingView authenticates to the broker). The MCP server scheme is TradingView-hosted.