Authentication

All requests require a Bearer token in the Authorization header.


Every endpoint in the TAAPI.IO v2 API requires an API key. Pass it as a Bearer token in the Authorization request header.

Header format

HTTP Header
Authorization: Bearer YOUR_API_KEY

There are no query-string or body-field alternatives. The key must be in the header on every request.

Getting an API key

  1. Create an account at taapi.io, then log in to the dashboard at app.taapi.io.
  2. Open API Keys. Your v2 key is the Production key (it starts with taapi_live_sk_). If you don't have one yet, generate it there. The Legacy API key (v1) on the same page only works with the old api.taapi.io API and is rejected by v2.
  3. Copy the key and use it in the Authorization header as shown above.

Example request

curl -G https://v2.taapi.io/indicator/rsi \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --data-urlencode "exchange=binance" \
  --data-urlencode "symbol=BTCUSDT" \
  --data-urlencode "timeframe=1h"

Error responses

If the header is missing or malformed, or the key is invalid, the API returns HTTP 401 with one of these messages:

401 Unauthorized
{ "error": "Missing or invalid Authorization header. Use: Authorization: Bearer <token>" }
{ "error": "Invalid or inactive token" }

See Errors for the full list of status codes.

Keeping your key safe

  • Do not embed your key in client-side code (browser JavaScript, mobile apps).
  • Store it in an environment variable and pass it at runtime.
  • If your key is compromised, regenerate it from the dashboard.

See the full list of indicators, or start for free.