TradersPost Futures Strategy Setup Demo
Supported Brokers
Click below to see the full list of supported futures brokers and prop firms.
Supported Tickers
TradersPost currently supports trading with the following futures tickers through TradeStation.
Here is an example of an alert with a hard-coded ticker:
{
"ticker": "MNQU2025",
"action": "buy"
}
Automating futures: the contract is the part to get right
A futures alert has to name one specific contract that expires on a specific date. Most of what is different about futures on TradersPost comes from that, so it is worth understanding before the first signal.
Send a dated contract symbol
Root, then month letter, then a four digit year. TradersPost converts it for each broker.
E-mini S&P 500, Dec 2026
Futures
You send ESZ2026
-
Tradovate
ESZ2026 -
TradeStation
ESZ26 -
tastytrade
ESZ2026
TradersPost converts the symbol before it places the order. See the futures symbol format docs.
Your chart and your broker can name the same contract differently
Root symbols are not always the same between TradingView and TradeStation. The documentation example is lumber.
TradingView calls it
LBR
TradeStation calls it
LB
TradingView ticker placeholder
"ticker": "{{ticker}}"
Sends whatever root the chart uses, which may not match your broker.
Hard-coded contract
"ticker": "LBX2026"
Type the dated contract into the alert message. TradersPost converts it for each broker.
MNQ1! can point at two contracts at once
TradersPost resolves a continuous symbol through its own current and next contract for the product. Your chart and your broker may switch on a different day. Sample dates for MNQZ2026, which expires on December 18, 2026.
| December 2026 | Fri 11 | Mon 14 | Tue 15 | Wed 16 | Thu 17 | Fri 18 |
|---|---|---|---|---|---|---|
| Your chartIts own switch date | MNQZ2026 | MNQH2027 | MNQH2027 | MNQH2027 | MNQH2027 | MNQH2027 |
| TradersPostIts own current contract | MNQZ2026 | MNQZ2026 | MNQZ2026 | MNQH2027 | MNQH2027 | MNQH2027 |
Safer habit: send the explicit contract, such as MNQZ2026, and change it when you roll.
On TradingView: turn on Continuous contract switch under Settings, then Events, to see planned switches.
Rolling ES from December to March
Sample dates. Check the exchange calendar for each contract.
-
Before Fri Dec 18
Switch the signal ticker
Send ESH2027 instead of ESZ2026 from here on. A dated contract never rolls on its own.
You do this
-
When the mapping switches
Continuous symbols roll
ES1! resolves to ESH2027 once TradersPost's current contract for ES switches, which can be a different day from your chart or your broker. ESZ2026 stays where it is.
TradersPost does this
-
Fri Dec 18 Key date
December expires
ESZ2026 stops trading. Close or roll any position first.
Exchange
-
When your broker rolls
Exit with the new contract
A position opened as ESZ2026 that the broker moved to ESH2027 is exited with ESH2027 in the ticker.
You do this
Take profit and stop loss are distances from your entry
Set the distance as a price offset, a percentage of the entry price, or a dollar PnL amount for the whole position.
- Contracts
- 2
- MNQ
- Point value
- $2
- per contract
- Entry
- 23,810.25
- buy
- PnL amount
- $100
- take profit and stop loss
TradersPost works out the distance
$100÷(2 × $2)=25 points
Resulting orders
- Take profit 23,835.25 +25 pts
- Entry 23,810.25 2 contracts
- Stop loss 23,785.25 −25 pts
A PnL based stop loss must be a stop or stop limit order, not a trailing stop.
Dynamic position sizing from a dollar or percent risk is not supported for futures. Use the PnL amount brackets to target a dollar outcome per trade.
Order support by connection
What each connection that trades futures accepts, as TradersPost sends it.
Supported Limited Not supported
| TradeStation | Tradovate | NinjaTrader | tastytrade | ProjectX | |
|---|---|---|---|---|---|
| Direction | |||||
| Long | Supported | Supported | Supported | Supported | Supported |
| Short | Supported | Supported | Supported | Supported | Supported |
| Sizing | |||||
| Fractional quantity | Not supported | Not supported | Not supported | Not supported | Not supported |
| Order types | |||||
| Market | Supported | Supported | Supported | Supported | Supported |
| Limit | Supported | Supported | Supported | Supported | Supported |
| Stop | Supported | Supported | Supported | Supported | Supported |
| Stop limit | Supported | Supported | Supported | Supported | Not supported |
| Trailing stop | Supported | Supported | Supported | Not supported | Supported |
| Time in force | |||||
| Day | Supported | Supported | Supported | Supported | Supported |
| Good till canceled | Supported | Supported | Supported | Supported | Not supported |
| Immediate or cancel | Supported | Supported | Supported | Not supported | Not supported |
| Fill or kill | Supported | Supported | Supported | Not supported | Not supported |
| At the open | Supported | Not supported | Not supported | Not supported | Not supported |
| At the close | Supported | Not supported | Not supported | Not supported | Not supported |
| Attached exits | |||||
| Bracket / OCO / OTO | Supported | Supported | Supported | Supported | Not supported |
| Trailing stop attached | Not supported | Supported | Supported | Not supported | Not supported |
| Accounts | |||||
| Paper trading | Supported | Supported | Supported | Not supported | Supported |
Bracket Orders, Take Profit, and Stop Loss (Futures)
For futures, you can define three types of brackets for take profit and stop loss:
Market Price Offset (Take profit amount, Stop loss amount)
A Market Price Offset is a fixed price distance from your entry price. This value is applied directly to the instrument's quoted price, including any decimal increments required by its tick size.

Example
If you enter MNQ at 25,125.25 and set:
- Take profit offset: 100
- Stop loss offset: 100
Your bracket orders will be placed at:
- Take profit: 25,225.25
- Stop loss: 25,025.25
This 100 represents a price movement, not a P&L amount.
Your actual profit or loss will depend on:
- Contract size
- Number of contracts traded
- The instrument's dollar value per point
TradersPost does not use a separate "points" concept internally. All futures brackets are calculated using market price offsets.
Market Price Percentage Offset (Take profit percent, Stop loss percent)
A Market Price Percentage Offset places your bracket at a percentage distance from entry.

Example
If you enter at 25,000 and set:
- Take profit: 1.00 percent
- Stop loss: 1.00 percent
1 percent of 25,000 is:
25,000 × 0.01 = 250
Your bracket orders will be placed at:
- Take profit: 25,250
- Stop loss: 24,750
These levels are calculated directly from the entry price, not from profit or loss in dollar terms.
Your actual P&L will depend on:
- The contract's dollar value per point
- The number of contracts traded
The percentage offset only determines how far the bracket is placed from entry in price terms.
PnL Amount (Take profit PnL amount, Stop loss PnL amount)
A PnL amount is the dollar profit or loss you want on the whole position. TradersPost converts it into a price distance from your entry (the formula and a worked example are in the figure above).
You can also send a PnL amount in your signal with takeProfit.pnlAmount and stopLoss.pnlAmount. A PnL-based stop loss must use a stop or stop limit order, not a trailing stop. See Webhooks for the full field reference.
Futures connections differ in symbols, quotes, and order types. The futures automation page walks through those differences and links each connection's notes.
Signals
It's easy to send signals to TradersPost using Webhooks from platforms like TradingView or TrendSpider. You just need to send JSON like the following to the webhook URL you create within TradersPost.
Enter Bullish
The buy action is a bullish signal. When TradersPost receives a buy signal, we will Buy To Cover any bearish (short) position for the ticker and Buy To Open a bullish (long).
{
"ticker": "NQH2022",
"action": "buy"
}
Exit Bullish
The exit action will exit any open position. So for example if you have a long shares position open, then TradersPost will Sell To Close those long contracts.
{
"ticker": "NQH2022",
"action": "exit"
}
Enter Bearish
The sell action is a bearish signal. When TradersPost receives a sell signal, we will Sell To Close any bullish (long) position for the ticker and Sell To Open a bearish (short) position.
{
"ticker": "NQH2022",
"action": "sell"
}
Exit Bearish
The exit action will exit any open position. So for example if you have a short contracts position open, then TradersPost will Buy to Cover those short contracts.
{
"ticker": "NQH2022",
"action": "exit"
}
Full Signal Example
You can optionally include a price and quantity in the signal that can then be used in the calculated orders that we send to your broker. Here is a full example signal.
{
"ticker": "NQH2022",
"action": "buy",
"price": 1420.50,
"quantity": 2
}
If you configure your strategy subscription to use limit orders and to use the signal quantity, then you will get a Buy Limit order for 2 contracts at a price of $1420.50.
Market Orders
Market orders can be rejected by your broker or exchange during major news announcements, when the exchange can go into reserve (see the figure above). When that happens you may receive a rejected order with the following reject reason:

To keep track of the news events that may cause market orders to be rejected you can use the following calendars.
- https://www.federalreserve.gov/newsevents/calendar.htm
- https://www.marketwatch.com/economy-politics/calendar
Contract Rollover
You are responsible for ensuring futures contract positions are exited before expiration or are rolled over manually. TradersPost does not automatically do anything special for futures contract positions based on expiration date.
If your position is held through a futures rollover, any exit signal must reference the new contract symbol. Once the broker rolls the position forward, exits must be sent using the rolled contract ticker.
For example, if you entered using MNQH2025 and the broker rolls the position to MNQM2025, your exit signal must use:
"ticker": "MNQM2025"
TradersPost maintains a current and next contract mapping for each futures root symbol. Continuous symbols such as NQ1! and NQ2! resolve through that mapping. The mapping is the same for every TradersPost customer and is derived from market data feeds, which may not be the broker you trade with.
- By default, each root's current and next contract is refreshed about once an hour from that contract data. If no current contract is reported, the existing mapping stays in place until the next successful refresh.
- For some products, TradersPost sets the current and next contracts itself instead of taking broker updates, and we can set the switch date to match the TradingView continuous contract switch date. A scheduled switch takes effect within a minute of its date.
Continuous Futures Symbols
Continuous symbols such as GC1! are accepted. TradersPost resolves them to a specific contract, and that resolution can differ from your broker and your charting platform around rollover periods. Explicit contract symbols such as GCJ2025 remain the recommended way to send futures signals.
A continuous symbol signal:
{
"ticker": "GC1!", // resolved by TradersPost, may differ around rollover
"action": "buy"
}
An explicit contract signal, recommended:
{
"ticker": "GCJ2025", // targets one contract month exactly
"action": "buy"
}
Read more about trading continuous futures on TradingView in our blog post.
Determining the Continuous Futures Contract Symbol
You can see the contract rollovers planned by TradingView using the Continuous contract switch event. On TradingView charts, head to Settings, click Events, and turn on "Continuous contract switch".

This will now show you an event at the bottom of the chart with a purple arrow that indicates when the contract rollover will take place and what ticker it will change from and to. You can use this to hard-code your alerts on the day of a rollover.

TradingView has also added the variable syminfo.current_contract to Pine Script. This would return the underlying contract for the current symbol if it is a continuous futures contract (na otherwise).
Futures Asset Class Subscription Settings Walkthrough
The subscription settings page is where you edit all settings for your individual subscriptions. It's also where you can override the settings you've sent in your webhook signal.
Auto Submit
Checking this will submit your subscription orders automatically to your broker. Otherwise, you will need to manually approve or reject each order.
Allowed Tickers
You can allow any ticker that is in your asset class or you can filter a subscription to only trade tickers you've added.
Futures tickers will need to be formatted like this: MNQ, NQ, MES.
Not MNQ1! (continuous contract) or MNQU2025 (specific contract)
Allowed Sides
Choose which trade directions are allowed: take both bullish and bearish trades, or restrict to just one side.
- Both (Bullish and Bearish)
- Bullish
- Bearish
- None
Allow Side Swapping (Advanced)
Normally, if a signal comes in for the opposite side, TradersPost will treat it like an exit signal by closing your position and stopping there. When this is turned on, we'll exit what you have and immediately open a new position on the opposite side.
Example: You are long 2 contracts and send the below JSON:
{
"ticker": "MNQU2025",
"action": "sell",
"quantity": "2",
"price": "23810.25",
"time": "2025-09-09T14:07:08Z",
"interval": "5"
}
Scenario 1:
- Allow side swapping
Your 2 contract long will immediately be closed, all open orders cancelled, and you'll be entered into a 2 contract short.
Scenario 2:
- Allow side swapping
Your 2 contract long will immediately be closed and all open orders cancelled. You will be out of all positions and net flat.
Subtract Exit Quantity from Signal Quantity (Advanced)
When side swapping is enabled, enable this option to take the exit quantity and subtract it from the signal quantity before side swapping. (Set Sides to Both, and enable both Side swapping and Allow signal override.)
Example: You are long 2 contracts and send the below JSON:
{
"ticker": "MNQU2025",
"action": "sell",
"quantity": "4",
"price": "23810.25",
"time": "2025-09-09T14:07:08Z",
"interval": "5"
}
Scenario 1:
- Subtract exit quantity from signal quantity
All open orders will be closed and 4 contracts will be subtracted from your open long, leaving you net short 2 contracts.
Scenario 2:
- Subtract exit quantity from signal quantity
Your 2 contract long will immediately be closed, all open orders cancelled, and you'll be entered into a 4 contract short.
Sides Isolated (Advanced)
If there is an open position on the opposite side, do not allow the trade signal to exit the position. (Sides must be set to Bullish or Bearish)
Example: You are short 2 contracts, have this setting set to "Bullish" and send the below JSON:
{
"ticker": "MNQU2025",
"action": "buy",
"quantity": "2",
"price": "23810.25",
"time": "2025-09-09T14:07:08Z",
"interval": "5"
}
Scenario 1:
- Sides Isolated
Your trade will fail and your short will not be exited.
Scenario 2:
- Sides Isolated
Your 2 contract short will immediately be closed, all open orders cancelled, and you'll be entered into a 2 contract long.
Trading Window
Trading Window
Define your trading windows. Trade signals received outside these windows will be ignored. "From" is inclusive; "To" is exclusive.
When trading windows are defined, any trading signals submitted outside those windows are ignored by default.
Enabling the Allow exits and cancels outside of trading windows option allows exit or cancel signals to be processed even if they occur outside the defined trading windows. This is helpful if you want to ensure entries happen within your window but still allow exits or cancellations at any time.
Example: You are in a 2 contract long that was entered during a trading window that ends at 4pm. It's now 4:01pm and the following signal is received:
{
"ticker": "MNQU2025",
"action": "sell",
"quantity": "2",
"price": "23810.25",
"time": "2025-09-09T16:01:08Z",
"interval": "5"
}
Scenario 1:
- Allow exits and cancels outside of trading windows
Your 2 contract long will immediately be closed, all open orders cancelled, and you'll be net flat.
Scenario 2:
- Allow exits and cancels outside of trading windows
Your 2 contract long will remain open and your sell trade will reject.
Position Size
Fixed Quantity
Hardcode a fixed quantity for each position instead of calculating a quantity dynamically.
This option allows you to specify a fixed quantity for your entries. For example, if you set the fixed quantity to 5, the strategy will always enter a quantity of 5 contracts when the trade is entered.
Amount Per Position (Not Supported)
Not a compatible position size option for the Futures asset class
Risk Per Position (Not Supported)
Not a compatible position size option for the Futures asset class
Percent of Equity (Not Supported)
Not a compatible position size option for the Futures asset class
Use Fractional Quantity (Not Supported)
Not a compatible option for the Futures asset class
Allow Add To Position
Allow adding to an existing open position. If this is not checked, trades will be rejected if there is already an open position.
Example: You are long 2 contracts and send the below JSON:
{
"ticker": "MNQU2025",
"action": "buy",
"quantity": "2",
"price": "23810.25",
"time": "2025-09-09T14:07:08Z",
"interval": "5"
}
Scenario 1:
- Allow Add To Position
Your 2 contract long will have 2 more contracts added to it, making it a net 4 contract long position.
Scenario 2:
- Allow Add To Position
Your 2 contract long will remain open, your add will reject, and you'll still be net 2 contracts long.
Signal Quantity Multiplier
Multiply the signal quantity by a fixed number to scale position size up or down. For example, a signal with quantity 2 and a multiplier of 2.5 results in a final quantity of 5. (Only applies when Allow signal override is enabled.)
The Signal Quantity Multiplier allows you to scale the quantity provided in a trade signal up or down by a fixed decimal value.
This multiplier is applied only if Allow signal override is enabled. When enabled, TradersPost will take the quantity value from the incoming webhook signal and multiply it by the number you provide here.
Example: You send in the following JSON
{
"ticker": "MNQU2025",
"action": "buy",
"quantity": "2",
"price": "23810.25",
"time": "2025-09-09T14:07:08Z",
"interval": "5"
}
Signal quantity multiplier: 2.5
Result: TradersPost will submit a market order for 5 contracts (2 × 2.5).
Use Cases
- You want to follow a signal provider’s trades, but your account is larger or smaller than theirs.
- You want to scale all trade sizes from a strategy, regardless of what quantity it sends.
- You want to reduce exposure (e.g. use
0.5to take half-size positions).
Notes
- Supports decimal values like
0.1,1.5,2,10, etc. - Can be used to scale down as well as up.
- Works with both whole and fractional quantities (if your broker supports fractional trading and Use fractional quantity is enabled).
- If the calculated final quantity results in a decimal and your broker does not support fractional shares/contracts, the value will be rounded down.
Tip
If you don't want to use the quantity from the signal, you can leave Allow signal override disabled and configure your own quantity calculation method instead.
Cancel
Cancel
Check this if you do not want TradersPost to cancel open orders before submitting new orders. Beware that if you disable this and you use take profit or stop losses in your broker and you send an exit signal, the broker may reject your exit order due to the take profit or stop loss orders still being open.
Example: You are long 2 contracts with a stop loss and take profit, and send the below JSON:
{
"ticker": "MNQU2025",
"action": "sell",
"sentiment": "flat",
"quantity": "2",
"price": "23810.25",
"time": "2025-09-09T14:07:08Z",
"interval": "5"
}
Scenario 1:
- Disable canceling open orders
Your 2 contract long will be exited, but the stop loss and take profit will not be cancelled.
Scenario 2:
- Disable canceling open orders
Your 2 contract long will immediately be closed, all open orders cancelled, and you'll be net flat.
Entries
Entry Order Type
If the broker you are using does not support quotes (Tradovate and ProjectX) you must always send a price in your signal if you are sending limit orders or bracket orders (ProjectX does not yet support brackets).
Choose the order type to use for entry orders. Your choices are below:
- Limit
- Market
- Stop Market
- Stop Limit
- Trailing Stop
For Trailing Stop orders, you'll also need to add one of the following
-
Entry Trail Amount (in dollars (market price offset) on the underlying futures ticker)
-
Entry Trail Percent (based off the % of the underlying futures ticker's market price). On Tradovate, NinjaTrader and ProjectX the percent becomes a fixed trail; see trailPercent.
-
Allow entry extended hours
Not supported for the Futures class
Entry Time In Force
By default, TradersPost will send the appropriate time in force of either gtc or day depending on the scenario and broker
Choose the entry time in force to use for entry orders. Your choices are below:
- Good For Day: The order is valid for the trading day and will be canceled if not executed by the end of the trading day
- Good Until Cancelled: The order is good until canceled and will remain active until it is executed or canceled. Fill Or Kill
- Immediate Or Cancel: The order is immediate or canceled, meaning it must be executed immediately or canceled.
- Fill Or Kill: The order is fill or kill, meaning it must be executed immediately in its entirety or canceled.
Entry Price
If the broker you are using does not support quotes (Tradovate and ProjectX) you must always send a price in your signal if you are sending limit orders or bracket orders (ProjectX does not yet support brackets).
For TradeStation (or other futures firms which support quotes) if you don't include a price and want to send a limit order or send a bracket with your entry, your choices are below for how you want TradersPost to estimate the signal price:
- Bid-ask midpoint
- Use ask for buys and bids for sells
- Always use ask
- Always use bid
- Use last price
Exits
Entry Order Type
If the broker you are using does not support quotes (Tradovate and ProjectX) you must always send a price in your signal if you are sending limit orders or bracket orders (ProjectX does not yet support brackets).
Choose the order type to use for exit orders. Your choices are below:
- Limit
- Market
- Stop Market
- Stop Limit
- Trailing Stop
For Trailing Stop orders, you'll also need to add one of the following
-
Exit Trail Amount (in dollars (market price offset) on the underlying futures ticker)
-
Exit Trail Percent (based off the % of the underlying futures ticker)
-
Allow exit extended hours
Not supported for the Futures class
Exit Time In Force
By default, TradersPost will send the appropriate time in force of either gtc or day depending on the scenario and broker
Choose the exit time in force to use for entry orders. Your choices are below:
- Good For Day: The order is valid for the trading day and will be canceled if not executed by the end of the trading day
- Good Until Cancelled: The order is good until canceled and will remain active until it is executed or canceled.
- Immediate Or Cancel: The order is immediate or canceled, meaning it must be executed immediately or canceled.
- Fill Or Kill: The order is fill or kill, meaning it must be executed immediately in its entirety or canceled.
Exit Price
If the broker you are using does not support quotes (Tradovate and ProjectX) you must always send a price in your signal if you are sending limit orders or bracket orders (ProjectX does not yet support brackets).
For TradeStation (or other futures firms which support quotes) if you don't include a price and want to send a limit order or send a bracket with your exit, your choices are below for how you want TradersPost to estimate the signal price:
- Bid-ask midpoint
- Use ask for buys and bids for sells
- Always use ask
- Always use bid
- Use last price
Take Profit / Stop Loss
Take Profit
If the broker you are using does not support quotes (Tradovate and ProjectX) you must always send a price in your signal if you are sending bracket orders (ProjectX does not yet support brackets).
Tradovate, TradeStation, and Tastytrade are the only futures brokers on TradersPost that support bracket orders (take profits / stop losses / trailing stops) that are attached with your entry or exit.
For take profits, you can have one of three choices:
- Take Profit Percent (based off the % of the underlying futures ticker)
- Take Profit Amount (based off of dollars (market price offset) on the underlying futures ticker)
- Take Profit PnL Amount (the dollar profit you want on the whole position, converted to a price offset; see Bracket Orders, Take Profit, and Stop Loss)
Scenario 1:
You send this signal with a take profit % as 5% in your subscription settings.
{
"ticker": "MNQU2025",
"action": "buy",
"quantity": "2",
"price": "23810.25",
"time": "2025-09-09T14:07:08Z",
"interval": "5"
}
You will be entered into a 2 contract long with a 2 contract limit sell at 25000 on MNQ.
The take profit % is not based on profit and loss on your portfolio, it's based on the underlying ticker. Even a small % on a futures ticker like MNQ will be a relatively huge amount for most traders. Make sure you understand that we are placing your take profit relative to the price where your futures ticker is trading in the signal that you send. In the above example, 23810.25 x 5% is a market price offset of $1,190.50 on MNQ.
Scenario 2:
You send this signal with a take profit amount as 250 in your subscription settings.
{
"ticker": "MNQU2025",
"action": "buy",
"quantity": "2",
"price": "23810.25",
"time": "2025-09-09T14:07:08Z",
"interval": "5"
}
You will be entered into a 2 contract long with a 2 contract limit sell at 24060.25 on MNQ.
The take profit amount is not based on profit and loss on your portfolio, it's based on a dollar market price offset on the underlying ticker. If you type in 250 it doesn't mean $250 profit on your P/L. It means 250 dollars on MNQ which for a 2-contract trade would be $1000 in profit on your P/L. It's up to you to figure out based on the number of contracts you're trading and the profit you want to achieve what value to write in the amount field. To set the dollar profit directly, use Take profit PnL amount instead.
Stop Loss
If the broker you are using does not support quotes (Tradovate and ProjectX) you must always send a price in your signal if you are sending bracket orders (ProjectX does not yet support brackets).
Tradovate, TradeStation, and Tastytrade are the only futures brokers on TradersPost that support bracket orders (take profits / stop losses / trailing stops) that are attached with your entry or exit.
For the stop loss order type, there are three choices:
- Stop Market
- Stop Limit
- Trailing Stop
As far as where the order will be placed relative to your entry, you have three choices:
- Stop Loss Percent (based off the % of the underlying futures ticker)
- Stop Loss Amount (based off of dollars (market price offset) on the underlying futures ticker)
- Stop Loss PnL Amount (the dollar loss you want to cap on the whole position, converted to a price offset; stop market and stop limit only; see Bracket Orders, Take Profit, and Stop Loss)
Scenario 1:
You send this signal with a stop loss % as 5% in your subscription settings.
{
"ticker": "MNQU2025",
"action": "buy",
"quantity": "2",
"price": "23810.25",
"time": "2025-09-09T14:07:08Z",
"interval": "5"
}
You will be entered into a 2 contract long with a 2 contract sell (stop market, stop limit, or trailing stop) at 22619.75 on MNQ.
The stop loss % is not based on loss on your portfolio, it's based on the underlying ticker. Even a small % on a futures ticker like MNQ will be a relatively huge amount for most traders. Make sure you understand that we are placing your stop loss / trailing stop relative to the price where your futures ticker is trading in the signal that you send. In the above example, 23810.25 - 5% is a market price offset of $1,190.50 on MNQ.
Scenario 2:
You send this signal with a stop loss amount as 250 in your subscription settings.
{
"ticker": "MNQU2025",
"action": "buy",
"quantity": "2",
"price": "23810.25",
"time": "2025-09-09T14:07:08Z",
"interval": "5"
}
You will be entered into a 2 contract long with a 2 contract sell (stop market, stop limit, or trailing stop) at 23560.25 on MNQ.
The stop loss amount is not based on profit and loss on your portfolio, it's based on the market price offset of the futures ticker. If you type in 250 it doesn't mean $250 loss on your P/L. It means 250 dollars on MNQ which for a 2-contract trade would be $1000 in loss on your P/L. It's up to you to figure out based on the number of contracts you're trading and the loss you want to limit what value to write in the amount field.
Retry
Retry
When TradersPost executes a trade, the first thing it does is communicate with the broker to fetch the state of the broker account and "plan the trade". This includes fetching current open positions, open orders, account balances, and any other information required to execute the trade. TradersPost then uses this information to determine the plan for executing the trade, which includes deciding whether to cancel any open orders for the ticker, exit the open position if it exists, or enter a new position. If there were any problems communicating with the broker or processing the trade plan, you will see this message.
Here is a list of the available retry settings:
- Max retries - The maximum number of times the system will retry the trade. If the trade fails after the maximum number of retries, the trade will be marked as failed.
- Delay in milliseconds - The delay between each retry attempt. The system will wait for this amount of time before retrying the trade.
- Delay multiplier - The multiplier to apply to the delay between each retry attempt. The system will multiply the delay by this value after each retry attempt. For example, if the delay is set to
1000milliseconds and the delay multiplier is set to2, the system will wait1000milliseconds before the first retry,2000milliseconds before the second retry,4000milliseconds before the third retry, and so on. - Max delay in milliseconds - The maximum delay between retry attempts. If the delay calculated by the delay multiplier exceeds this value, the system will use this value as the delay.
