TradingView Rithmic Webhook Setup: Use the Generated Configuration

Prepare the configuration

Confirm the intended account/System, execution contract, event source, quantity and exit arrangement with the current generator. Check the current TradingView plan comparison and required two-factor authentication. A plan upgrade alone does not grant exchange data or provider permission for automation.

Documented sequence

1. Verify the receiving service's supported Rithmic connection and expected account.
2. Generate the message for the actual indicator/strategy route and intended contract.
3. Copy the application-supplied endpoint without editing its private token/path by guesswork.
4. Create the TradingView alert with the script/integration's required event and message.
5. Enable the webhook notification in the current dialog and enter that endpoint.
6. Check alert duration and the saved symbol/timeframe/inputs.
7. Save only after confirming the configuration, then use the appropriate permitted verification process.

The official webhook guide documents the HTTP message behavior. It does not certify a particular recipient's order handling.

TradingView field examples

Source: PickMyTrade TradingView alert guide, checked 8 October 2026. These are field-location examples. Its historical screenshots contain a different chart/payload example and an older .trade endpoint; do not copy those values into the Rithmic .io workflow. Use the message and endpoint from the current matching generator. For an indicator, choose that indicator's intended condition; for a strategy, follow its required event source rather than assuming a generic price-crossing event is equivalent.

Verify without conflating outcomes

Keep uncertain requests separate from confirmed failures. TradingView's retry rule applies to specified server-error responses; a receiving service must have its own documented handling. Do not resend blindly because the original outcome is unknown.

Vendor examples of the result screens

Sources: PickMyTrade Alerts guide and Orders guide, checked 8 October 2026. Compare time, connection, account, symbol and identifiers in your own records. An alert status and an order status describe different stages; reconcile the broker's own order/fill history before concluding that a trade filled. These vendor examples are separate illustrations, not a verified matched execution chain.

Changing an existing script alert

TradingView documents saved script/input/chart context. Changing the chart does not change that snapshot. Recreate the script alert when that context must change, then verify the service's separate symbol and exit configuration. Prevent two old/new trade alerts from overlapping through the supported workflow.

Evidence scope and checks for your account

On 8 October 2026, the authenticated PickMyTrade session showed an existing Rithmic connection marked Connected and two available accounts. The current generator produced an unsaved documentation message for those two destinations. The displayed 8 September–9 October history range contained no alert logs or orders. The one existing saved configuration was for IB, not Rithmic. No message was sent, no TradingView alert was saved, and no order was submitted.

The redacted two-destination message and selected tick calculation are now retained. To validate your own workflow, compare the matching TradingView event, resolved execution contract, recipient response and actual broker result. A 2xx webhook response establishes neither an accepted order nor a fill. Do not use the temporary public Rithmic trial as a substitute for the eligible Protocol account required by the documented receiver.