Directional Movement Index

The Directional Movement Index (DMI) is a popular technical indicator used by traders to assess the strength and direction of a trend in a financial instrument. It was developed by J. Welles Wilder and is particularly useful in identifying trending markets. The DMI consists of three returned values: the Average Directional Index (ADX), the Positive Directional Indicator (PDI), and the Negative Directional Indicator (NDI).

The ADX is the primary component of the DMI and measures the strength of a trend, regardless of its direction. It provides traders with a numerical value ranging from 0 to 100. A higher ADX value indicates a stronger trend, while a lower value suggests a weaker or non-existent trend. Traders often look for ADX values above 25 to confirm the presence of a significant trend.

The PDI and NDI are secondary components of the DMI and provide insights into the direction of the trend. The PDI measures the strength of upward price movements, while the NDI measures the strength of downward price movements. Both indicators range from 0 to 100. When the PDI is above the NDI, it suggests a bullish trend, indicating buying pressure. Conversely, when the NDI is above the PDI, it suggests a bearish trend, indicating selling pressure.

Traders use the DMI to identify potential entry and exit points in the market. When the ADX is rising, it indicates an increasing trend strength, and traders may consider opening positions in the direction of the trend. Conversely, when the ADX is falling or below the 25 threshold, it suggests a weakening trend, and traders may consider closing their positions or waiting for a new trend to develop.

In summary, the DMI is a valuable technical indicator that helps traders assess the strength and direction of a trend. The ADX provides a measure of trend strength, while the PDI and NDI indicate the direction of the trend. By using these three values together, traders can make more informed decisions and improve their trading strategies.

Note: in our API responses, we use “mdi” (“minus DI”) instead of NDI, but that is just a naming difference.

Get started with the dmi

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


API response

The dmi endpoint returns a JSON response like this:

	"adx": 32.79044853218805,
	"pdi": 25.418284332339116,
	"mdi": 16.2144851753789
Example response from TAAPI.IO when querying dmi 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 dmi value X amount of candles back. So, if you’re fetching the dmi on the hourly and you want to know what the dmi was 5 hours ago, set backtrack=5. The default is 0 and a maximum is 50.
Optional Integer
The backtracks parameter returns the dmi value calculated on every candle for the past X candles. For example, if you want to know what the dmi 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

Sets the number of candles used in the indicator calculation.

Default: 14

More examples

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

Let's say you want to know what the dmi 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:

		"adx": 32.79044853218805,
		"pdi": 25.418284332339116,
		"mdi": 16.2144851753789,
		"backtrack": 0
		"adx": 33.61224435711242,
		"pdi": 26.850700351883955,
		"mdi": 13.637651656666161,
		"backtrack": 1
		"adx": 33.68747874284775,
		"pdi": 28.455274009324466,
		"mdi": 14.452625430566297,
		"backtrack": 2
		"adx": 33.76850038902427,
		"pdi": 25.55361869672962,
		"mdi": 15.39959430031488,
		"backtrack": 3
		"adx": 34.458830651075225,
		"pdi": 26.836067489261417,
		"mdi": 14.86593906114697,
		"backtrack": 4
		"adx": 34.901512796964504,
		"pdi": 27.52384425514056,
		"mdi": 15.246935550044734,
		"backtrack": 5
		"adx": 35.378247415614496,
		"pdi": 31.432608529617735,
		"mdi": 13.029229033864567,
		"backtrack": 6
		"adx": 34.915696790780075,
		"pdi": 32.33937815659913,
		"mdi": 13.842575151314435,
		"backtrack": 7
		"adx": 34.5205953669006,
		"pdi": 34.481460099049166,
		"mdi": 11.899848218648598,
		"backtrack": 8
		"adx": 33.43088117143078,
		"pdi": 33.99259165990072,
		"mdi": 12.60002136324693,
		"backtrack": 9

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