openapi: 3.2.0 info: description: "## Overview\n\nWelcome to Twelve Data developer docs — your gateway to comprehensive financial market data through a powerful and easy-to-use API.\nTwelve Data provides access to financial markets across over 50 global countries, covering more than 1 million public instruments, including stocks, forex, ETFs, mutual funds, commodities, and cryptocurrencies.\n\n## Quickstart\n\nTo get started, you'll need to sign up for an API key. Once you have your API key, you can start making requests to the API.\n\n### Step 1: Create Twelve Data account\n\nSign up on the Twelve Data website to create your account [here](https://twelvedata.com/register). This gives you access to the API dashboard and your API key.\n\n### Step 2: Get your API key\n\nAfter signing in, navigate to your [dashboard](https://twelvedata.com/account/api-keys) to find your unique API key. This key is required to authenticate all API and WebSocket requests.\n\n### Step 3: Make your first request\n\nTry a simple API call with cURL to fetch the latest price for Apple (AAPL):\n\n```\ncurl \"https://api.twelvedata.com/price?symbol=AAPL&apikey=your_api_key\"\n```\n\n### Step 4: Make a request from Python or Javascript\n\nUse our client libraries or standard HTTP clients to make API calls programmatically. Here’s an example in [Python](https://github.com/twelvedata/twelvedata-python) and [Node.js](https://github.com/twelvedata/twelvedata-node):\n\n#### Python (using official Twelve Data SDK):\n\n```python\nfrom twelvedata import TDClient\n\n# Initialize client with your API key\ntd = TDClient(apikey=\"your_api_key\")\n\n# Get latest price for Apple\nprice = td.price(symbol=\"AAPL\").as_json()\n\nprint(price)\n```\n\n#### JavaScript (Node.js):\n\n```javascript\nimport { MarketDataApi, CreateConfig } from \"@twelvedata/twelvedata-node\";\n\nconst config = CreateConfig('your_api_key');\nconst api = new MarketDataApi(config);\n\nasync function main() {\n const response = await api.getPrice({\n symbol: \"AAPL\",\n });\n console.log(response.data);\n}\n\nmain().catch(console.error);\n```\n\n### Step 5: Perform correlation analysis between Tesla and Microsoft prices\n\nFetch historical price data for Tesla (TSLA) and Microsoft (MSFT) and calculate the correlation of their closing prices:\n\n```python\nfrom twelvedata import TDClient\nimport pandas as pd\n\n# Initialize client with your API key\ntd = TDClient(apikey=\"your_api_key\")\n\n# Fetch historical price data for Tesla\ntsla_ts = td.time_series(\n symbol=\"TSLA\",\n interval=\"1day\",\n outputsize=100\n).as_pandas()\n\n# Fetch historical price data for Microsoft\nmsft_ts = td.time_series(\n symbol=\"MSFT\",\n interval=\"1day\",\n outputsize=100\n).as_pandas()\n\n# Align data on datetime index\ncombined = pd.concat(\n [tsla_ts['close'].astype(float), msft_ts['close'].astype(float)],\n axis=1,\n keys=[\"TSLA\", \"MSFT\"]\n).dropna()\n\n# Calculate correlation\ncorrelation = combined[\"TSLA\"].corr(combined[\"MSFT\"])\nprint(f\"Correlation of closing prices between TSLA and MSFT: {correlation:.2f}\")\n```\n\n### Authentication\n\nAuthenticate your requests using one of these methods:\n\n#### Query parameter method\n```\nGET https://api.twelvedata.com/endpoint?symbol=AAPL&apikey=your_api_key\n```\n\n#### HTTP header method (recommended)\n```\nAuthorization: apikey your_api_key\n```\n\n##### API key useful information\n

Demo API key (apikey=demo) available for demo requests
Personal API key required for full access
Premium endpoints and data require higher-tier plans (testable with trial symbols)

\n\n### API endpoints\n\n Service | Base URL |\n---------|----------|\n REST API | `https://api.twelvedata.com` |\n WebSocket | `wss://ws.twelvedata.com` |\n\n### Parameter guidelines\n

Separator: Use & to separate multiple parameters
Case sensitivity: Parameter names are case-insensitive (symbol=AAPL = symbol=aapl)
Multiple values: Separate with commas where supported

\n\n### Response handling\n\n#### Default format\nAll responses return JSON format by default unless otherwise specified.\n\n#### Null values\nImportant: Some response fields may contain `null` values when data is unavailable for specific metrics. This is expected behavior, not an error.\n\n##### Best Practices:\n

Always implement null value handling in your application
Use defensive programming techniques for data processing
Consider fallback values or error handling for critical metrics

\n\n#### Error handling\nStructure your code to gracefully handle:\n

Network timeouts
Rate limiting responses
Invalid parameter errors
Data unavailability periods

\n\n##### Best practices\n

Rate limits: Adhere to your plan’s rate limits to avoid throttling. Check your dashboard for details.
Error handling: Implement retry logic for transient errors (e.g., 429 Too Many Requests).
Caching: Cache responses for frequently accessed data to reduce API calls and improve performance.
Secure storage: Store your API key securely and never expose it in client-side code or public repositories.

\n\n## Errors\n\nTwelve Data API employs a standardized error response format, delivering a JSON object with `code`, `message`, and `status` keys for clear and consistent error communication.\n\n### Codes\n\nBelow is a table of possible error codes, their HTTP status, meanings, and resolution steps:\n\n Code | status | Meaning | Resolution |\n --- | --- | --- | --- |\n **400** | Bad Request | Invalid or incorrect parameter(s) provided. | Check the `message` in the response for details. Refer to the API Documentation to correct the input. |\n **401** | Unauthorized | Invalid or incorrect API key. | Verify your API key is correct. Sign up for a key here. |\n **403** | Forbidden | API key lacks permissions for the requested resource (upgrade required). | Upgrade your plan here. |\n **404** | Not Found | Requested data could not be found. | Adjust parameters to be less strict as they may be too restrictive. |\n **414** | Parameter Too Long | Input parameter array exceeds the allowed length. | Follow the `message` guidance to adjust the parameter length. |\n **429** | Too Many Requests | API request limit reached for your key. | Wait briefly or upgrade your plan here. |\n **500** | Internal Server Error | Server-side issue occurred; retry later. | Contact support here for assistance. |\n\n### Example error response\n\nConsider the following invalid request:\n\n```\nhttps://api.twelvedata.com/time_series?symbol=AAPL&interval=0.99min&apikey=your_api_key\n```\n\nDue to the incorrect `interval` value, the API returns:\n\n```json\n{\n \"code\": 400,\n \"message\": \"Invalid **interval** provided: 0.99min. Supported intervals: 1min, 5min, 15min, 30min, 45min, 1h, 2h, 4h, 8h, 1day, 1week, 1month\",\n \"status\": \"error\"\n}\n```\n\nRefer to the API Documentation for valid parameter values to resolve such errors.\n\n## Libraries\n\nTwelve Data provides a growing ecosystem of libraries and integrations to help you build faster and smarter in your preferred environment. Official libraries are actively maintained by the Twelve Data team, while selected community-built libraries offer additional flexibility.\n\nA full list is available on our [GitHub profile](https://github.com/search?q=twelvedata).\n\n### Official SDKs\n

Python: twelvedata-python
Node.js: twelvedata-node
Go: twelvedata-go
Java: twelvedata-java
R: twelvedata-r-sdk
CLI: twelvedata-cli

\n\n### AI integrations\n

Twelve Data MCP Server: Repository — Model Context Protocol (MCP) server that provides seamless integration with AI assistants and language models, enabling direct access to Twelve Data's financial market data within conversational interfaces and AI workflows.
Twelve Data integration for OpenClaw: Clawhub skill — Integration for the OpenClaw platform, allowing users to leverage Twelve Data's API within their OpenClaw applications.
Twelve Data NEAR Agent: NEAR Agent — Access Twelve Data's API directly from NEAR's AI agent platform, enabling users to retrieve financial data and insights within their NEAR AI agent workflows.

\n\n### Spreadsheet add-ons\n

Excel: Excel Add-in
Google Sheets: Google Sheets Add-on

\n\n### Community libraries\n\nThe community has developed libraries in several popular languages. You can explore more community libraries on [GitHub](https://github.com/search?q=twelvedata).\n

C#: TwelveDataSharp
JavaScript: twelvedata
PHP: twelvedata
Go: twelvedata
TypeScript: twelve-data-wrapper

\n\n### Other Twelve Data repositories\n

searchindex (Go): Repository — In-memory search index by strings
ws-tools (Python): Repository — Utility tools for WebSocket stream handling

\n\n### API specification\n

OpenAPI / Swagger: Access the complete API specification in OpenAPI format. You can use this file to automatically generate client libraries in your preferred programming language, explore the API interactively via Swagger tools, or integrate Twelve Data seamlessly into your AI and LLM workflows.

" title: Twelve Data Technical Indicator API version: 0.0.1 servers: - url: https://api.twelvedata.com/ security: - authorizationHeader: - '[]' - queryParameter: - '[]' tags: - name: technical_indicator paths: /ad: get: description: The Accumulation/Distribution (AD) endpoint provides data on the cumulative money flow into and out of a financial instrument, using its closing price, price range, and trading volume. This endpoint returns the AD line, which helps users identify potential buying or selling pressure and assess the strength of price movements. operationId: GetTimeSeriesAd parameters: - description: Symbol ticker of the instrument. E.g. `AAPL`, `EUR/USD`, `ETH/BTC`, ... in: query name: symbol schema: type: string x-go-name: Symbol x-order: '10' x-required-group: symbol x-go-name: Symbol x-order: '10' x-required-group: symbol example: AAPL - description: Filter by international securities identification number (ISIN). ISIN access is activating in the Data add-ons section in: query name: isin schema: type: string x-go-name: Isin x-order: '25' x-required-group: symbol x-go-name: Isin x-order: '25' x-required-group: symbol example: US0378331005 - description: The FIGI of an instrument for which data is requested. This parameter is available on the Ultra plan (individual) and the Enterprise plan (business) and above. in: query name: figi schema: type: string x-go-name: Figi x-order: '20' x-required-group: symbol x-go-name: Figi x-order: '20' x-required-group: symbol example: BBG000B9Y5X2 - description: The CUSIP of an instrument for which data is requested. CUSIP access is activating in the Data add-ons section in: query name: cusip schema: type: string x-go-name: Cusip x-order: '26' x-required-group: symbol x-go-name: Cusip x-order: '26' x-required-group: symbol example: '594918104' - description: Interval between two consecutive points in time series in: query name: interval required: true schema: $ref: '#/components/schemas/IntervalEnum' x-go-name: Interval x-order: '30' example: 1min - description: Number of data points to retrieve. Supports values in the range from `1` to `5000`. Default `30` when no date parameters are set, otherwise set to maximum in: query name: outputsize schema: default: 30 format: int64 type: integer x-go-name: PageSize x-order: '80' x-go-name: PageSize x-order: '80' - description: Exchange where instrument is traded in: query name: exchange schema: type: string x-go-name: Exchange x-order: '40' x-go-name: Exchange x-order: '40' example: NASDAQ - description: Market Identifier Code (MIC) under ISO 10383 standard in: query name: mic_code schema: type: string x-go-name: MicCode x-order: '50' x-go-name: MicCode x-order: '50' example: XNAS - description: The country where the instrument is traded, e.g., `United States` or `US` in: query name: country schema: type: string x-go-name: Country x-order: '60' x-go-name: Country x-order: '60' example: United States - description: The asset class to which the instrument belongs in: query name: type schema: $ref: '#/components/schemas/TypeEnum' x-go-name: Type x-order: '70' example: Common Stock - description: 'Timezone at which output datetime will be displayed. Supports:

1. Exchange for local exchange time
2. UTC for datetime at universal UTC standard
3. Timezone name according to the IANA Time Zone Database. E.g. America/New_York, Asia/Singapore. Full list of timezones can be found here

Interval Limitation: The timezone parameter is only applicable for intraday intervals (less than 1 day). For intervals of 1day, 1week, or 1month, the timezone parameter is ignored, and data is strictly returned in the Exchange local time.

Take note that the IANA Timezone name is case-sensitive' in: query name: timezone schema: default: Exchange type: string x-go-name: Timezone x-order: '135' x-go-name: Timezone x-order: '135' - description: 'Can be used separately and together with `end_date`. Format `2006-01-02` or `2006-01-02T15:04:05` Default location:

Forex and Cryptocurrencies - UTC
Stocks - where exchange is located (e.g. for AAPL it will be America/New_York)