TAAPI.IO

Finance

TAAPI.IO is a technical analysis API with 262 indicators across crypto and stock exchanges. Agents fetch RSI, MACD, moving averages, and any other indicator for a symbol, run bulk calculations across markets, compute indicators from your own candles, and pull raw OHLCV data.

15 actions API key available

TAAPI.IO website Platform Documentation Capability data verified 2026-08-25

A scheduled poll runs after the timeframe's candle is expected to have closed

Get Bulk Indicators computes the whole indicator set across the watched markets in one request

The agent confirms every construct and indicator id it asked for actually came back

The agent confirms the values were computed on the last closed candle, not the one still forming

The crossing, its inputs, and the candle it came from are written to the research log

The signal posts to the desk with the exact parameters that produced it

The desk decides whether to act, and nothing downstream moves until they answer

What This Integration Enables

TAAPI.IO is a calculation service rather than a data feed, and that is the reason to reach for it. You are not buying prices, you are buying the arithmetic on top of them: 262 indicators across crypto and stock exchanges, computed by somebody else, returned as a value your flow can branch on. Teams end up here because maintaining their own indicator library is a job nobody wanted and everybody inherited.

FlowRunner agents can call any of the 262 by name, use the eight named shortcuts for the most common ones, or hand over their own candle array when the market is one TAAPI does not list. Bulk calculation matters more than it sounds: many indicators across several markets come from a single candle fetch per market, which is what keeps a real strategy affordable and is the correct answer to a rate limit rather than a retry. The connectors layer also carries the two vendor behaviors that quietly change what a result means, the result count that switches a scalar into an array and the backtrack setting that decides whether you are reading a closed candle or a live one.

Without FlowRunner

Indicator math maintained in house Somebody on the team owns the moving average and oscillator implementations, and the edge cases in them

Signals that flicker A rule reads a candle that is still forming, so the same rule answers differently minute to minute

Silent gaps in a batch One indicator fails inside a multi market request and is simply absent from the result

With FlowRunner

The math is the vendor's problem Indicator values arrive already calculated across the crypto and stock exchanges the plan covers

Signals tied to a closed candle A rule reads the last closed candle, so the same inputs give the same answer twice

Incomplete batches get caught The agent checks that every requested construct returned before anything acts on the result

Use Case Scenarios

One request instead of a fan out

A watchlist agent needs a dozen indicators across several markets every timeframe. Rather than looping, it calls Get Bulk Indicators with one construct per market and every indicator inside it, so each market costs a single candle fetch. The results land in PostgreSQL keyed by the construct and indicator ids the flow chose, and a summary of what moved posts to Slack. The same job that would have hit a rate limit as separate calls finishes as one.
Testing a rule against history you already hold

The research team has candle history in a warehouse that TAAPI does not carry, from a venue or a private feed. The agent pulls the series from Snowflake, passes it into Get Indicators From Candles, and gets the same indicator set computed against that history instead of against an exchange. Results append back to the warehouse so a rule can be evaluated over past data before it is ever pointed at a live market. Because these results are never cached, each pass is recomputed, so the flow batches them deliberately rather than calling in a loop.
Cross referencing a signal before anyone reads it

An indicator crossing on its own is thin evidence. When Get RSI or Get MACD returns a level worth attention, the agent enriches it before it reaches a person: current market data from CoinGecko or Marketstack, the symbol's own recent candles from Get Candles, and the position record from Airtable. The desk receives one message containing the signal, its parameters, and the surrounding context, rather than an alert that sends someone to open three tabs.

Human-in-Loop Highlight

TAAPI will hand back a confident looking number in two situations where it is not yet an answer, and neither of them raises an error. The default backtrack setting calculates on the candle that is still forming, whose value keeps changing until it closes, so a rule evaluated there can fire and un-fire within the same minute. And inside Get Bulk Indicators, a single indicator that fails is silently absent from the response unless verbose mode is switched on, so a strategy can evaluate with a missing leg and never notice. The agent treats both as a full stop. It checks that the values came from the last closed candle, and that every construct and indicator id it requested is present. When either check fails, it posts to the desk: "SuperTrend flipped to long on BTC/USDT 1h, but the value was computed on the candle still forming and the ATR leg is missing from the batch. Re-run against the closed candle, or hold?" No order, no position change, and no client facing alert goes out on a number the agent cannot vouch for. That is human-in-the-loop applied where it belongs, at the moment a reading becomes a decision.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

15 actions

Indicators

Get Indicator Calculates any of the 262 indicators the vendor publishes, chosen by friendly name or by the vendor's own slug. Indicator specific parameters pass through unchanged, so an indicator without a named shortcut is still fully reachable.
Get RSI Calculates the relative strength index for a symbol and timeframe, with its period spelled out as its own parameter.
Get MACD Calculates moving average convergence divergence. It answers named keys for the line, the signal, and the histogram rather than a single value, so a flow reads the one it needs.
Get EMA Calculates an exponential moving average over the period you name.
Get SMA Calculates a simple moving average over the period you name.
Get Bollinger Bands Calculates the upper, middle, and lower bands, each returned under its own key.
Get Stochastic Calculates the stochastic oscillator, returning the K and D lines separately.
Get ATR Calculates average true range, the usual input for sizing a stop or measuring volatility.
Get SuperTrend Calculates SuperTrend and returns a direction alongside the value, which is one of the few indicators a flow can branch on without comparing anything itself.

Bulk and Custom Candles

Get Bulk Indicators Computes many indicators across several markets in one request, with each market's indicators sharing a single candle fetch. The affordable way to run a real watchlist, and the right response to a rate limit. Switch verbose on while building, because it is the only way to see which single indicator in a batch failed.
Get Indicators From Candles Computes several indicators against a candle array you supply instead of an exchange and symbol. Used for markets TAAPI does not list, private feeds, and evaluating a rule over history you already hold.
Get Indicator From Candles Computes one indicator against a candle array you supply. The single indicator form of the same idea.

Market Data

Get Candles Returns raw open, high, low, close, and volume data for a symbol and timeframe. Used to show a person the surrounding market when an indicator alone would not be enough to decide.
List Exchanges Returns the exchanges TAAPI covers. Coverage is not the same as access, since which exchanges your plan may query is a separate limit.
List Symbols Returns the symbols an exchange accepts, in that exchange's own spelling. The authority for symbol format, because the same market is written differently from one venue to the next.

Frequently Asked Questions

What can FlowRunner do with TAAPI.IO?

FlowRunner agents can run Get Indicator, Get RSI, and Get MACD in TAAPI.IO, plus 12 more actions.

Does connecting TAAPI.IO to FlowRunner require OAuth?

No. TAAPI.IO connects to FlowRunner with an API key, no OAuth flow required.

Can TAAPI.IO trigger a FlowRunner workflow automatically?

TAAPI.IO doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with TAAPI.IO

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us