TB Hook My Trade
TradingView to Binance automation SaaS

Turn TradingView alerts into Binance orders with a clean client dashboard

This platform is built for real webhook execution: TradingView alert comes in, your SaaS validates it, acknowledges fast, and routes the order to Binance with tenant-level isolation, logs, and risk controls.

Start Single Package Client Login View Setup Guidelines
2FA Required TradingView webhook setup should use an account with 2FA enabled.
Fast Acknowledgement Webhook endpoint should answer in about 1 to 2 seconds and stay under 3 seconds.
Production Ports TradingView webhook requests should be exposed on public HTTPS over ports 80 or 443.
Live Execution Pattern TradingView Alert -> SaaS -> Binance
POST /webhook/your-client-slug
request validated secret matched
tenant identified your-client-slug
side: BUY | symbol: BTCUSDT
order routed to Binance Futures API
dashboard + logs updated for the client
{ "secret": "MY_SHARED_SECRET", "exchange": "binance", "symbol": "BTCUSDT", "side": "BUY", "orderType": "MARKET", "qty": "0.001", "strategy": "ema_cross_15m", "timestamp": "{{timenow}}" }
4 source IPsAllowlist TradingView webhook IPs on production.
Signed ordersRoute authenticated, signed requests to Binance only from your backend.
Async-safeReturn 200 fast, then process order logic and logging cleanly.
Webhook response target Under 3 seconds to avoid TradingView timeout issues
Allowed public ports 80 / 443 for TradingView webhook delivery
Tenant access Separate client login URL, branding, settings and audit trail
Binance execution Backend-side validation, risk checks and signed order requests
Workflow

Simple architecture, production-minded behavior

The platform is designed around the easiest reliable flow for Binance automation: TradingView Alert -> webhook server -> validation layer -> Binance order execution -> logs and dashboard.

1

TradingView sends the alert

Use a JSON alert body so the webhook receives structured trading data like symbol, side, quantity and strategy name.

2

Webhook validates instantly

We verify secret, tenant route, schema and basic risk rules before acknowledging the request quickly.

3

Binance order is placed

The backend prepares the request, signs it securely and sends it to Binance from the server side.

Client-specific workspace

Every tenant gets isolated credentials, webhook routing, dashboard visibility and login access.

Audit trail that teams can trust

Webhook history, trade results and account status are kept visible so support and clients can move faster.

Built for live and staged rollout

Use testnet while onboarding, then switch to live execution after strategy and quantity checks are stable.

Guidelines

What to configure before going live

This section is written for real usage so clients and internal teams know exactly what to set up on TradingView, what your server must handle, and what safety rules should never be skipped.

TradingView setup

  • Enable 2FA on the TradingView account before webhook-based alerts are used.
  • Set the webhook URL to your tenant route like https://yourdomain.com/webhook/your-client-slug.
  • Send alerts in valid JSON so the backend can parse symbol, side, quantity and strategy cleanly.

Server rules

  • Expose the public endpoint on HTTPS using ports 80 or 443 only.
  • Return a fast success response and shift heavier execution logic to a worker-safe path.
  • Use shared secret checks, schema validation and duplicate alert protection on every request.

Risk controls

  • Restrict allowed symbols and enforce max position size before sending orders to Binance.
  • Keep paper mode and live mode clearly separated during onboarding.
  • Add a kill switch and monitor failed or uncertain exchange execution states.

Recommended production checklist

  • Allowlist TradingView source IPs: 52.89.214.238, 34.212.75.30, 54.218.53.128, 52.32.178.7.
  • Never send Binance private API keys directly from TradingView alerts.
  • Verify exchange responses and log the final order state for support and reconciliation.
Included

What this landing and platform communicate clearly

One straightforward offer for fast onboarding

Instead of multiple confusing plans, the page now focuses on one working package with practical setup guidance, client login access and a clean explanation of how TradingView to Binance execution actually happens.

See Package Open Client Login
Pricing

One package. Clear scope. Easy to start.

You asked for a single package, so the landing page now presents only one simple monthly offer that is easy for clients to understand and easier for sales conversations too.

Single Active Package

Hook My Trade Client Automation

Rs. 2,000/month

Best for traders and small client accounts that want TradingView alerts routed to Binance with a ready client dashboard.

  • Client login page with Google sign-in support
  • Tenant-specific webhook URL and dashboard access
  • Binance credential storage and testnet/live configuration
  • Webhook validation, trade logging and execution history
  • Support-ready setup guidance for TradingView webhook onboarding
Request Setup Open Client Login
Contact

Talk to sales and get your client workspace configured

Fill the form and the inquiry will go directly into the admin dashboard. This is useful when a client wants setup help, onboarding support, or a quick walkthrough before starting the Rs. 2,000 monthly package.

Direct admin visibility Every form submission is stored and visible inside the admin panel under the inquiries tab.
Single package context Each lead is captured against the active Hook My Trade Client Automation package.
Clean client handoff Name, email, phone, company and message stay available for fast follow-up.

Sales Inquiry Form

Request Setup

Selected package Hook My Trade Client Automation - Rs. 2,000/month