Pulse ProtocolPrivate test version. Pulse Protocol is not open to the public yet: access is for testing and early access, by invitation only, and nothing is sold. It is operated by a company currently being incorporated in the Seychelles; its registration details will be published before any public commercial launch. The legal documents on this site are drafts that are not in force.
TradingView integration
A TradingView alert can open, add to, or close a position in Pulse. Here is exactly what travels, what does not, and what permissions Pulse needs on your exchange.
Pulse Protocol is not affiliated with, endorsed by, or partnered with TradingView. Pulse receives standard webhook alerts, which is a feature TradingView offers to its users on its own terms. TradingView is a trademark of its owner.
How it works
- In Pulse, create a preset or a Signal bot: pair, side, size, leverage, take-profits, stop. This is where the money decisions live.
- Pulse gives you a webhook URL containing a secret token. Treat it like a password.
- In TradingView, create an alert on your strategy and paste that URL into the Webhook URL field. The alert message names the action.
- When the alert fires, TradingView calls the URL, Pulse authenticates the token, finds the matching preset or bot, and executes your configuration.
What the message can and cannot say
The message carries intent only. Size, leverage, targets and stop come from what you configured in Pulse, so a compromised or malformed alert cannot ask for a larger position than the one you set. The exact format depends on what the alert drives.
For a preset
A preset already knows its pair and its side. The message only says whether to open or to close:
{"action": "open"}{"action": "close"}For a Signal bot
A Signal bot can trade several pairs, so the message names the pair and the direction:
{"action": "enter_long", "pair": "BTCUSDT"}{"action": "exit_long", "pair": "BTCUSDT"}Accepted actions: enter_long, enter_short,
exit_long, exit_short and close_at_market_price.
Anything else is refused and recorded, never guessed. An optional "id" field
lets Pulse ignore an alert that TradingView sends twice.
No secrets in your alert message. The token belongs in the webhook URL field, never in the message body, never in a screenshot, and never in a shared chart. Anyone holding the URL can fire that preset.
API permissions Pulse needs
| Permission | Needed | Why |
|---|---|---|
| Read account & positions | Yes | To show balance, positions and to know what to protect. |
| Place & cancel orders (futures) | Yes | To execute the trade you configured. |
| Withdraw / transfer funds | Never | Pulse never asks for it and has no code that uses it. Do not enable it. |
Create the key without withdrawal rights. An API key configured without withdrawal permission does not allow Pulse to make a withdrawal. Always check the permissions directly with your exchange: they are set there, and that is the only place they can be confirmed. Where your exchange offers IP whitelisting, use it. See Security.
Test it in simulation first
Point the alert at a preset on the simulation account and let it fire a few times. You will see the orders, the fills and the rejections with real prices and no money at risk. Only then switch the account to LIVE. The distinction is shown on every page and is never ambiguous.