Features & Settings

Security Risks to Brokerage Accounts When Sending Signals

While webhook URLs act like passwords, the risk to brokerage accounts is minimal as TradersPost encrypts API keys and limits permissions to trading only.

Tom Hartman

Marketing

2 Min Read Reviewed by Mike Christensen Fact-checked by Mike Christensen
BluSky — The Future of Trading. Prop firm futures trading. Sign up at BluSky.pro.
Update history
  1. Correction

    Current TradersPost documentation no longer supports automatic API revocation after a password change, so the broker-specific claim has been corrected while the article's broader security guidance remains accurate.

A common concern for traders using automated platforms like TradersPost is whether sending signals from services like TradingView poses any security risks to their brokerage accounts. This issue was discussed during a recent office hours session, highlighting the safeguards and potential vulnerabilities.

Security Concerns with Webhook URLs

When using TradingView to send signals to TradersPost, a unique webhook URL is generated. This URL functions similarly to a password, and if someone gains access to it, they could potentially send orders through your TradersPost account. However, they would only be able to place orders tied to a strategy that allows those tickers, meaning there’s no financial gain other than causing disruption .

The primary risk comes from accidentally exposing the webhook URL. If it’s shared publicly or in unsecured channels (e.g., Discord), someone could exploit it to send signals on your behalf. TradersPost mitigates this by allowing you to easily regenerate a new URL, which invalidates the previous one .

API Key Security and Broker Integration

TradersPost integrates with your brokerage using API keys. These keys are encrypted and stored securely, with encryption at rest, minimizing the risk of a breach. Even in the unlikely event of a security failure, attackers wouldn’t be able to withdraw funds or add bank accounts, as TradersPost only has permission to execute trades, cancel orders, and fetch account balances .

Moreover, TradersPost stores broker access tokens securely and does not store your broker username or password, adding an extra layer of protection. This helps safeguard your account while allowing TradersPost to connect to your brokerage for trading 1.

Conclusion

While there is a minimal risk associated with exposing webhook URLs, TradersPost has implemented several security features to protect your brokerage account. The system is designed to prevent unauthorized withdrawals or fund transfers, focusing on trading permissions only. Users should treat webhook URLs like passwords and avoid sharing them in unsecured environments.

References

1 traderspost.io, Important Disclosures and Disclaimers

  • Post-Only Order: How It Works

    Post-only orders guarantee maker-side execution or cancellation. Learn how they work, why exchanges cancel or reprice them, and when to use one.

  • Difference Between Mark And Last In TOS

    Mark price and last price mean different things on trading platforms. Learn how each is calculated, why they diverge, and which to use for stops.

  • Broker Rules Now Follow the Asset Class

    Learn why a setting disappeared in TradersPost: broker rules for order types, shorting, and time in force now apply per asset class, not per broker.

  • Walk-Forward Optimization Trading Guide

    Master walk-forward optimization trading to test strategies across market regimes, reduce curve fitting, and prepare alerts for disciplined automation.

Ready to put what you read into practice?

Free 7-day trial

Set-up in 3 minutes

Paper account for testing

By continuing, you agree to the TradersPost Terms of Service and Privacy Policy. This site is protected by reCAPTCHA.