ThetaData · Authentication Profile
Thetadata Authentication
Authentication
ThetaData authenticates at the session level, not per HTTP request. The published OpenAPI declares security: [] because the local REST API served by the Theta Terminal (127.0.0.1:25503/v3) is an unauthenticated loopback surface; credentials are supplied when the terminal (or the Python library client) starts, which opens an authenticated session to ThetaData's MDDS servers. Requests are additionally IP-pinned to the first requester (error 476 WRONG_IP) and a single terminal session is enforced (error 478 INVALID_SESSION_ID).
ThetaData secures its APIs with apiKey and credentials across 2 declared security schemes, as derived from its OpenAPI definitions.
FinancialMarket DataOptionsStocksIndicesReal-TimeHistorical DataTrading
Methods: apiKey, credentials
Schemes: 2
OAuth flows:
API key in: cli-argument, environment-variable, dotenv-file
Security Schemes
api_key apiKey
credentials credentials