PineConnector Webhook: Message Format and Demo Verification
A PineConnector webhook carries a TradingView alert to a configured execution connection. A delivered alert is not yet a broker fill: message validation, connection state, order rules, and broker acceptance are separate steps. Use PineConnector's documented command format rather than assuming that an arbitrary JSON payload will be accepted.
Use the documented URL and message format
PineConnector's syntax reference currently specifies https://webhook.pineconnector.com for TradingView's Webhook URL field. The Message field uses its comma-separated syntax. A demonstration of the format is:
LicenseID,buy,EURUSD,vol_lots=0.01,sl_pips=20,tp_pips=40
LicenseID is a placeholder, and EURUSD must match the intended broker symbol or an explicitly configured mapping. The lot size and stop distances are illustrative syntax values, not a suitable trade size for every account. Do not send the example to a live connection as a test.
This is not a JSON object with ticker, side, and account keys. Valid JSON syntax alone says nothing about whether a receiver understands the message. TradingView supports different content types, but the receiver's schema determines what it can process.
Choose the connection you actually use
The current PineConnector setup guide presents Edge, which hosts MT5 and the PineConnector EA, as well as self-hosted setup options. Edge has its own supported-server and plan requirements. A user-managed Windows VPS is therefore not universally required for every current setup.
Check the platform, exact broker server, available connection, and EA configuration before creating alerts. Do not infer cTrader, TradeStation, MT4, or third-party EA support from an MT5 example. Follow the instructions for the selected product and version rather than combining old installation steps with a new service.
Verify the route in stages
- Prepare a demo account and confirm that the chosen connection points to that account.
- Enable TradingView's two-factor authentication and confirm webhook access on the current plan.
- Copy the documented URL and a command compatible with the active EA settings.
- Follow PineConnector's setup test and inspect the alert, bridge, and terminal evidence.
- Verify the actual demo order's symbol, direction, size, stops, and account. A connection test alone does not establish all of these.
Use the provider's current test procedure; this page does not assume that every TradingView alert dialog has a universal “Send Test” button. Review the generated command before submitting it.
Match alert timing to the trading rule
An indicator condition, an alert() event, and a strategy order-fill event are different triggers. Decide which one your execution route expects. If a rule uses a completed bar, configure confirmation consistently, but do not assume that “once per bar close” prevents duplicates across multiple alerts or connections.
TradingView alerts retain a saved copy of the script and settings. After changing the code or inputs, review the running alert and recreate it when needed. A chart that looks correct with new settings does not prove that an older saved alert uses them.
Protect routing and authentication information
TradingView's webhook guide requires two-factor authentication and warns against putting sensitive login information in messages. Use PineConnector's supported signal-authentication configuration if available for your setup. Do not invent an HMAC field and assume that the EA validates it.
A License ID can route to accounts attached to that connection. Confirm the intended destination before enabling an alert, especially when several accounts are involved. Arbitrary JSON account labels do not establish routing behavior.
Keep broker passwords out of alert messages, screenshots, and shared troubleshooting examples. Enter credentials only in the provider's documented account-connection flow.
Diagnose the first missing step
| Evidence | Next check |
|---|---|
| No TradingView alert event | Condition, schedule, symbol, and saved alert configuration |
| Alert fired but delivery failed | Webhook URL and TradingView delivery status |
| Delivery occurred but command was rejected | License ID, syntax, authentication, and connection selection |
| EA processed the command but no order exists | Terminal logs, broker symbol, volume rules, trading permissions, and rejection reason |
| Order exists with unexpected parameters | Command units, EA settings, mapping, and any duplicate routes |
Record timestamps from the same incident and account for clock differences when measuring latency. Alert-to-receiver latency, order-submission latency, and fill latency are different measurements. No fixed sub-300 ms execution or slippage reduction is established here.
After a disruption, reconcile the account before blindly resending a command. Repetition may create another order if the first succeeded but its acknowledgement was missed. The appropriate recovery action depends on observed order state and the provider's supported controls.