Get started with the lantern

Simply make an HTTPS [GET] request or call in your browser:


The lantern endpoint returns a JSON response like this:

  "timestampHuman": "2021-01-14 16:00:00 (Thursday) UTC",
  "timestamp": 1610636400,
  "open": 39577.53,
  "high": 40100,
  "low": 39294.7,
  "close": 39610.24,
  "volume": 6415.4483510003165
Example response from TAAPI.IO when querying lantern endpoint.

API parameters

Required String
The secret which is emailed to you when you request an API key.
Required String
The exchange you want to calculate the indicator from: binance, binancefutures or one of our supported exchanges. For other crypto / stock exchanges, please refer to our Client or Manual integration methods.
Required String
Symbol names are always uppercase, with the coin separated by a forward slash and the market: COIN/MARKET. For example: BTC/USDT Bitcoin to Tether, or LTC/BTC Litecoin to Bitcoin...
Required String
Interval or time frame: We support the following time frames: 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.
Optional Integer
The backtrack parameter removes candles from the data set and calculates the lantern value X amount of candles back. So, if you’re fetching the lantern on the hourly and you want to know what the lantern was 5 hours ago, set backtrack=5. The default is 0 and a maximum is 50.
Optional Integer
The backtracks parameter returns the lantern value calculated on every candle for the past X candles. For example, if you want to know what the lantern was every hour for the past 12 hours, you use backtracks=12. As a result, you will get 12 values back.
Optional String
The 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.
Optional Boolean
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 helpful when requesting multiple backtracks.
New Optional Boolean
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.
New Optional String
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.
Optional Integer

Default: 3

More examples

Let's say you want to know the lantern 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 lantern values on each of the past X candles in one call

Let's say you want to know what the lantern 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 backtracks=10 parameter:


Here's the example response:

    "timestampHuman": "2021-01-14 16:00:00 (Thursday) UTC",
    "timestamp": 1610636400,
    "open": 39577.53,
    "high": 40100,
    "low": 39294.7,
    "close": 39524.37,
    "volume": 6434.031963000314,
    "backtrack": 0
    "timestampHuman": "2021-01-14 15:00:00 (Thursday) UTC",
    "timestamp": 1610632800,
    "open": 38977.98,
    "high": 39762.7,
    "low": 38788.19,
    "close": 39577.53,
    "volume": 9975.288968,
    "backtrack": 1
    "timestampHuman": "2021-01-14 14:00:00 (Thursday) UTC",
    "timestamp": 1610629200,
    "open": 38257.97,
    "high": 39000,
    "low": 38154.22,
    "close": 38977.66,
    "volume": 5153.841864,
    "backtrack": 2
    "timestampHuman": "2021-01-14 13:00:00 (Thursday) UTC",
    "timestamp": 1610625600,
    "open": 38365.86,
    "high": 38427.11,
    "low": 37707,
    "close": 38257.96,
    "volume": 3638.08289,
    "backtrack": 3
    "timestampHuman": "2021-01-14 12:00:00 (Thursday) UTC",
    "timestamp": 1610622000,
    "open": 38488.05,
    "high": 38622.6,
    "low": 38060,
    "close": 38365.86,
    "volume": 3014.522816,
    "backtrack": 4
    "timestampHuman": "2021-01-14 11:00:00 (Thursday) UTC",
    "timestamp": 1610618400,
    "open": 37938.1,
    "high": 38490.49,
    "low": 37869.1,
    "close": 38487.37,
    "volume": 3151.658946,
    "backtrack": 5
    "timestampHuman": "2021-01-14 10:00:00 (Thursday) UTC",
    "timestamp": 1610614800,
    "open": 38370.01,
    "high": 38464.13,
    "low": 37862.04,
    "close": 37938.11,
    "volume": 3551.706141,
    "backtrack": 6
    "timestampHuman": "2021-01-14 09:00:00 (Thursday) UTC",
    "timestamp": 1610611200,
    "open": 38199.52,
    "high": 38786.1,
    "low": 38192.64,
    "close": 38370.01,
    "volume": 3936.809626,
    "backtrack": 7
    "timestampHuman": "2021-01-14 08:00:00 (Thursday) UTC",
    "timestamp": 1610607600,
    "open": 37837.2,
    "high": 38596.92,
    "low": 37703.09,
    "close": 38198.34,
    "volume": 5294.802195,
    "backtrack": 8
    "timestampHuman": "2021-01-14 07:00:00 (Thursday) UTC",
    "timestamp": 1610604000,
    "open": 37529.11,
    "high": 38100,
    "low": 37440,
    "close": 37837.21,
    "volume": 3705.587755,
    "backtrack": 9

Looking for even more integration examples in different languages like NodeJS, PHP, Python, Curl or Ruby? Continue to [GET] REST - Direct documentation.