logo
API
API

Documentation

May 11, 2025

Intohook API, Webhooks & Automation Guide 🔌

Discover how to integrate with Intohook’s webhook system, use automation, and explore the full potential of our API and backend tools.

Webhook to AWS Setup

This section dives deep into the backend infrastructure and what happens behind the scenes when your strategy fires. It also explains how to interpret logs and handle common trading errors with confidence.

When your TradingView strategy sends an alert, it doesn’t go directly to the exchange — it flows through our Central HUB, a highly optimized infrastructure that ensures low-latency trade execution globally.

🚀 Here's How It Works:
  1. TradingView Strategy Fires Alert
    You’ve configured your strategy, created the alert, and it triggers on your chart.

  2. Webhook is Sent to Our HUB
    The alert is routed to your unique webhook URL (which you got from the Telegram bot). This URL connects to our Central HUB — a distributed set of servers located in multiple global regions (North America, Europe, Asia) to reduce latency and slippage.

  3. Smart Parsing & Execution
    Our system reads the alert, parses the settings (like exchange, volume, leverage, etc.), and routes it to the appropriate execution engine for that exchange — Binance, Bybit, KuCoin, and others.

  4. Privacy First
    We do NOT log, save, or store any alert content.

    • API keys and secrets are only used in memory during the execution process.

    • Your trade information is processed instantly and discarded securely.

  5. Execution Confirmation in Telegram
    Once executed, you'll receive a log of the trade (or any error) in real-time directly in Telegram.

🔒 Designed for privacy, speed, and reliability. You control your trades. We just deliver them with precision.

Error Handling & Logs

Not every trade can go through — and that’s where logs come in. Our Telegram bot gives you detailed responses for every alert processed, so you're never left guessing what went wrong.

✅ Success Log

If your trade executes successfully, you'll get:

  • ✅ Symbol, price, order type, volume

  • ✅ Exchange confirmation (market or limit order)

  • ⏱ Timestamp of execution and response speed in milliseconds

❌ Common Errors & What They Mean

Here are some of the most frequent error messages, especially from Binance and Bybit, and how to resolve them:

Error

Meaning

min_notional / MIN_NOTIONAL

Your volume is too small. Increase your $ size or check exchange limits.

INSUFFICIENT_BALANCE

Your account doesn’t have enough funds to place the trade.

symbol not supported

You’re using a symbol not available on the selected exchange.

API_KEY_INVALID / INVALID_KEY

The API key is incorrect, expired, or doesn’t have trading permissions.

timestamp expired

Time sync issue. Ensure device time is synced or try again.

order would trigger immediately

Using a limit order too close to market price — try using a market order.

passphrase mismatch

Your passphrase (from the Telegram bot) is incorrect or missing.


🛠 Debugging Tips

  • Double-check your API keys: Ensure trading permission is enabled and IP whitelist (if used) allows our servers.

  • Ensure symbol matches your chart and is valid for the exchange (e.g., BYBIT:BTCUSDT, not BINANCE:BTCUSD).

  • Reconfirm strategy settings — volume, leverage, and order type — especially if using percentage-based volume.

💡 Everything is built to give you visibility, speed, and control — with full transparency.

Go Back