Ichimoku Cloud
The Ichimoku Cloud is a collection of technical indicators that show support and resistance levels, as well as momentum and trend direction. It does this by taking multiple averages and plotting them on the chart. It also uses these figures to compute a “cloud” which attempts to forecast where the price may find support or resistance in the future. This implementation returns the standard cloud values [conversion line, base line, spanA, spanB], but returns along with it the spanA-B values for the current price, as well as for the lagging period.
Get started with the ichimoku
Simply make an HTTPS [GET] request or call in your browser:
[GET] https://api.taapi.io/ichimoku?secret=MY_SECRET&exchange=binance&symbol=BTC/USDT&interval=1h
API response
The ichimoku
endpoint returns a JSON response like this:
{
"conversion": 22767.545,
"base": 21722.95,
"spanA": 22265.4975,
"spanB": 21458.95,
"currentSpanA": 19534.550000000003,
"currentSpanB": 19444.485,
"laggingSpanA": 19304.7425,
"laggingSpanB": 19270.5
}
Example response from TAAPI.IO when querying ichimoku endpoint.
API parameters
binance
, binancefutures
or one of our supported exchanges. For other crypto / stock exchanges, please refer to our Client or Manual integration methods.
BTC/USDT
Bitcoin to Tether, or LTC/BTC
Litecoin to Bitcoin...
1m
, 5m
, 15m
, 30m
, 1h
, 2h
, 4h
, 12h
, 1d
, 1w
. So if you're interested in values on hourly candles, use interval=1h
, for daily values use interval=1d
, etc.
backtrack
parameter removes candles from the data set and calculates the ichimoku value X amount of candles back. So, if you are fetching the ichimoku on the hourly and you want to know what the ichimoku was 5 hours ago, set backtrack=5
. The default is 0
.
chart
parameter accepts one of two values: candles
or heikinashi
. candles
is the default, but if you set this to heikinashi
, the indicator values will be calculated using Heikin Ashi candles. Note: Pro & Expert Plans only.
true
or false
. Defaults to false
. By setting to true
the API will return a timestamp with every result (real-time and backtracked) to which candle the value corresponds. This is especially helpful when requesting a series of historical values using the results
parameter.
1685577600
1731456000
If you only use fromTimestamp, the API will return all results from that time until present.
true
or false
. Defaults to true
. By setting to false
, the API will ensure that there are no candles missing. This often happens on lower timeframes in thin markets. Gaps will be filled by a new candle with 0 volume, and OHLC set the the close price of the latest candle with volume.
number
or max
. Use this parameter to access historical values on the past X candles until the most recent candle. Use max
to return all available historical values. Returns an array with the oldest value on top and most recent value returned the last.
Default: 9
Default: 26
Default: 52
Default: 26
More examples
Let's say you want to know the ichimoku
value on the last closed candle on the 30m
timeframe. You are not interest in the real-time value, so you use the backtrack=1
optional parameter to go back 1 candle in history to the last closed candle.
[GET] https://api.taapi.io/ichimoku?secret=MY_SECRET&exchange=binance&symbol=BTC/USDT&interval=30m&backtrack=1
Get ichimoku values on each of the past X candles in one call
Let's say you want to know what the ichimoku
daily value was each day for the previous 10 days. You can get this returned by our API easily and efficiently in one call using the results=10
parameter:
[GET] https://api.taapi.io/ichimoku?secret=MY_SECRET&exchange=binance&symbol=BTC/USDT&interval=1d&results=10
Looking for even more integration examples in different languages like NodeJS, PHP, Python, Curl or Ruby? Continue to [GET] REST - Direct documentation.