A TradeStation PickMyTrade setup starts with the destination: SIM or Live, the connected account and the instrument that account will trade. It ends with evidence from TradeStation that the intended order reached the intended account. A successful login, a TradingView notification or a processing message alone cannot establish that a trade filled.
Table of Contents
- Key takeaways
- What changes between TradeStation SIM and Live?
- How do you connect TradeStation to PickMyTrade?
- How should you configure the first alert?
- Which exit workflow should your TradeStation PickMyTrade setup use?
- How do you verify the first order?
- Why is the connection active but the trade missing?
- What must you change when moving from SIM to Live?
- Frequently asked questions
- Start with a route you can verify
This guide explains how to configure the route through pickmytrade.io, choose an exit workflow and check the first entry and exit. It also covers the checks needed when moving from simulation to live trading. Use the current account interface alongside the linked documentation; account permissions and available settings can differ.
Key takeaways
– Choose SIM or Live deliberately, then confirm the destination account. – Match the generated message to the indicator or strategy event supplying it. – Decide who controls exits before enabling entries. – Verify broker orders, fills, positions and remaining protection separately. – Recheck the whole route when changing environments or running strategy settings.
What changes between TradeStation SIM and Live?
TradeStation describes its SIM API as a paper-trading environment with fictitious accounts, simulated funds and instant simulated fills. Its Live API uses a different endpoint. That separation makes SIM useful for checking message routing and order instructions, while live execution still needs its own verification. See TradeStation’s SIM versus Live documentation.
A strategy backtest on TradingView does not select TradeStation SIM for you. These are different parts of the setup: the backtest models strategy behavior, while the broker environment determines where an outgoing order is directed. An automation test should name both, rather than using “paper trading” as a description for the entire route.
| Check | SIM test | Live verification |
|---|---|---|
| Destination | Confirm the simulation account | Confirm the intended live account |
| Order instructions | Check symbol, side and quantity | Recheck instructions and live permissions |
| Execution | Inspect simulated results | Inspect actual acceptance and fills |
| Exits | Test the complete close workflow | Verify position and remaining working orders |
An immediate SIM fill is not evidence that a live limit order will fill immediately. Market liquidity, available size and price movement still matter. Use simulation to validate the instructions and resulting account state, rather than treating its execution results as a forecast of live performance.
How do you connect TradeStation to PickMyTrade?
PickMyTrade’s TradeStation connection and indicator guide documents a TradeStation Connection control, a username field and an environment choice of Sim or Live. After connecting, Generate Alert provides the configuration used to produce the webhook URL and message. Follow the current interface if labels have changed.
- Open the TradeStation connection flow in your PickMyTrade account.
- Enter the requested TradeStation login identifier and deliberately select Sim or Live.
- Complete the official authorization flow presented by the service.
- Confirm that the expected destination account is available before generating an alert.
- Record the connection, environment and account together so the route is easy to recognize later.
If an expected account is missing, resolve that issue before editing account identifiers in a message. Confirm the login, selected environment and access to the account. A similar account name is not enough: compare the actual destination shown by the broker and the account selected for automation.
Keep credentials and webhook secrets out of screenshots, shared notes and public support posts. A useful setup record identifies the destination without exposing the information that authorizes access to it.
How should you configure the first alert?
Generate the message for the broker, account, instrument and signal source you actually intend to use. PickMyTrade’s guide distinguishes Indicator from Strategy and lists instrument choices including stocks, futures and options. Use its generated payload as the starting point, rather than adapting an unrelated broker’s JSON example.
Check the quantity and intended instrument before copying the output. For a futures route, compare the chart symbol with the executable contract selected for TradeStation. For options, identify the specific contract and intended action using the dedicated TradeStation options guide. A broad instrument category does not identify an individual option contract.
TradingView offers different event sources for strategy alerts: order fills, alert() calls, or both. Its technical alerts guide describes these choices. Select the source that matches the integration instructions and the script’s messages. Selecting both requires checking whether the script could send two actionable messages for the same trading decision.
Copy the generated webhook URL and message into the relevant TradingView alert fields. Then inspect the saved alert. A message saved in PickMyTrade and a message running in TradingView are separate configuration records; keep a note of which running alert uses which destination.
Which exit workflow should your TradeStation PickMyTrade setup use?
Choose the exit method before testing an entry. The PickMyTrade TradeStation strategy guide describes three arrangements: No SL/TP for strategy-driven exits, Attach SL/TP for attached protection, and Multiple Exits for alert-driven scale-outs. In the documented Multiple Exits mode, SL/TP cannot be attached to the entry order.
Write down the expected result in plain language. For example: “The entry opens the intended quantity, and a later strategy exit closes it.” Alternatively: “The entry is followed by attached protection, whose broker status I will verify.” These statements give the test a specific outcome to check.
When combining entry signals, partial exits and protective orders, account for what remains after the first close. A strategy may believe it still holds a position after a broker-side stop has filled. Before allowing later messages to act, verify how the selected configuration handles that difference. Do not assume every exit instruction is automatically synchronized.
For scale-outs, compare the original quantity, each intended reduction and the final remaining position. Also inspect working orders after the position becomes flat. A correct first entry is only part of the test; the completed position lifecycle matters.
How do you verify the first order?
Follow one identifiable test event through TradingView, PickMyTrade and TradeStation. The purpose is to establish what each system actually recorded. Preserve the event time and time zone so records can be compared accurately. The following checklist is a recommended verification method, rather than a claim that every interface uses identical status labels.
- Confirm that the intended TradingView alert triggered and inspect its resolved message.
- Locate the corresponding request in PickMyTrade and read the processing result or error.
- Find the matching broker order in the intended TradeStation environment and account.
- Compare the instrument, side, quantity, order type and any specified price.
- Inspect execution details and the resulting position, including any partial fill.
- Check the intended exit or protective orders, then verify the final position after closing.
An order record and a fill record answer different questions. An accepted but unfilled limit order may still be waiting for its conditions. A rejected request needs its rejection reason investigated. A filled entry with absent protection is a different issue again. Treat these outcomes separately when deciding what to fix.
If a request times out or the result is unclear, inspect TradeStation before sending it again. A missing response does not establish that the broker has no order. Repeating an uncertain entry could increase exposure if the original request already succeeded.
Why is the connection active but the trade missing?
An active connection establishes less than a completed order test. Start with the earliest stage where evidence is missing, then work forward. Avoid changing several unrelated settings at once: that makes it harder to identify the original problem or determine whether the next test fixed it.
- No TradingView event: check the alert condition, active state and expiry.
- TradingView event but no matching PickMyTrade request: inspect webhook configuration and delivery information.
- PickMyTrade error: use the exact error text to check the account, message or configuration involved.
- Broker rejection: investigate the recorded broker reason, such as an invalid instruction or account restriction.
- Working order without a fill: inspect price conditions, session and remaining quantity.
- Unexpected position: compare earlier fills, manual trades and other alerts using the same account.
For support, provide the environment, account identifier, instrument, event time with time zone, relevant request reference and broker order ID if available. Include exact error text and redacted screenshots. Describe the observed state—rejected, working, partially filled or filled—rather than reporting only “not working.”
What must you change when moving from SIM to Live?
Treat the move as a new destination check. Confirm the Live connection and account, inspect the generated instructions and review every running alert that could send orders. Check the live account’s permissions, available buying power or margin, relevant market access and intended quantity before enabling the route.
Changing a chart’s strategy settings does not update an existing strategy alert. TradingView explains that the alert runs a separate server-side copy; affected strategy alerts must be deleted and recreated to incorporate those changes. See TradingView’s strategy alert documentation.
Do not assume changing an environment selector also rewrites all saved messages or running alerts. Inspect each record that contains routing information. Disable obsolete routes deliberately, while accounting for any open positions and working orders they previously created. Stopping future alerts does not itself establish that those positions are closed.
Before leaving the setup unattended, confirm the intended account is receiving events and the exit workflow behaves as expected. Keep a route record with the broker, environment, account, symbol, quantity, alert name and exit method. That record helps distinguish a configuration change from an execution issue later.
Frequently asked questions
No. A backtest and the TradeStation destination are separate. Verify Sim or Live in the broker connection and confirm the account receiving the order. A simulated strategy result is not evidence that an outgoing webhook targets a simulation account.
No. TradeStation documents simulated instant fills in SIM. Use that environment to check integration behavior and account routing. It does not establish live liquidity, queue position, fill price or execution timing, so inspect actual live order outcomes separately.
Use the mode that matches the signal source and PickMyTrade’s instructions for it. Check the TradingView event selection as well as the PickMyTrade dropdown. The script must supply the messages the chosen route expects, including the intended exit instructions.
First check the broker’s order and position records. There may be a working order, partial fill or successful submission whose response was delayed. Establish the original request’s state before deciding whether another order is needed.
Confirm the remaining broker position and inspect working orders. If the intended outcome was flat, verify that it is flat in the correct account. Review any remaining protective or entry orders so the next signal starts from an understood account state.
Start with a route you can verify
The most useful first test has a clearly identified account, instrument, quantity and exit plan. Confirm each stage from signal to broker record, then repeat the destination checks when changing environments. Use the PickMyTrade documentation hub to open the current TradeStation guide alongside your configuration before enabling the route.
Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.
Also Checkout: Futures Position Sizing: Ticks, Points and Planned Risk
Connect your alerts with PickMyTrade — automated trade execution, no coding required. Start free →