Twelve Data
DATA · COMMERCE & FINANCE
Quotes, time series, indicators, and fundamentals across global markets.
Connect Twelve Data with Fabriq Developer
Your user pastes their Twelve Data credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Twelve Data in practice
Twelve Data bills in API credits per minute rather than requests, and the spread across endpoints is a hundred to one: a standard quote costs 1 credit per symbol while market movers and exchange schedule cost 100 each. On the free Basic plan, which gets 8 credits a minute and 800 a day, a single market-movers call is more than twelve minutes of budget.
Rate limits
- Credits refresh each minute. Basic (free): 8 API credits/minute and 800 requests/day, plus 8 trial WebSocket credits.
- Grow: 377 API credits/minute, no daily cap. Pro: 1,597 API plus 1,500 WebSocket. Ultra: 10,946 API plus 10,000 WebSocket.
- Per-endpoint credit cost: time series, quote, price and end of day 1 per symbol; time series cross 5 per request; cross listings 40; market movers 100; exchange schedule 100.
- WebSocket credits are charged per subscribed symbol, at weights that vary by endpoint.
Worth knowing
- Because credits are charged per symbol, a 50-symbol batch is 50 credits, not one request — the free plan cannot fetch a 50-name watchlist in a single minute.
- The per-minute credit allowance is the binding limit on paid plans; the daily cap only exists on Basic, so the failure mode differs between a trial and production.
- Credit costs are documented per endpoint rather than per response size, so an agent has to carry a cost table to predict its own throughput.
- WebSocket and REST credits are separate allowances, so a streaming integration cannot borrow from its REST budget.
Checked against Twelve Data API documentation (2026-09-29), Twelve Data pricing and credit allowances (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Twelve Data behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.