Error Codes Reference

This document provides a comprehensive reference for all error codes and messages you may encounter when using SignalBee. Use Ctrl+F to search for specific error messages.

---

How to Find Error Details

Signal History Page

View all received signals and their processing status:

• Status: success, pending (order accepted by the exchange but not yet filled, e.g. a resting limit order), rejected, or failed
• Reason: Machine-readable code (e.g., duplicate_signal)
• Message: Human-readable explanation
• Click on any signal to see full details

Order History Page

View all orders and their execution results:

• Status: filled, pending (accepted by the exchange, waiting to fill — a resting limit order stays pending until it fills or is cancelled), rejected, failed, or cancelled
• Error Message: Exchange-provided error details for failed orders
• Exchange Response: Raw response from the exchange API

Webhook Test Results

Test your webhook configuration before going live:

• Shows validation results for all fields
• Simulates order execution without placing real orders
• Displays balance and size limit checks

---

Signal Validation Errors

These errors occur when your webhook payload fails validation. Fix your TradingView alert message or webhook configuration.

Example Valid Payload

{
  "webhook_secret": "your-webhook-secret",
  "side": "buy",
  "symbol": "BTC-USDT",
  "quantity_type": "percentage",
  "quantity": 50,
  "source_timestamp": "{{timenow}}"
}

---

API/Webhook Error Codes

These errors are returned in the HTTP response when your webhook request fails.

Response Format

Accepted Response (HTTP 202):

{
  "status": "queued",
  "signal_id": "uuid",
  "message": "Signal accepted for processing"
}

Note: Production webhooks are processed asynchronously. A 202 response means the signal was accepted and queued for execution. Use the /webhook/test/{user_id} endpoint for synchronous validation and testing.

Test Endpoint Response (HTTP 200):

The test endpoint (/webhook/test/{user_id}) returns the full order result synchronously:

{
  "status": "success",
  "message": "Order would be executed successfully",
  "signal_id": "uuid",
  "order_id": "uuid",
  "exchange": "binance",
  "order_side": "BUY",
  "quantity": "0.001",
  "price": "45000.00",
  "reason": ""
}

Rejected/Failed Response (from test endpoint):

{
  "status": "rejected",
  "message": "Trading pair not whitelisted",
  "signal_id": "uuid",
  "reason": "pair_not_whitelisted"
}

Error Response (validation error):

{
  "status": "error",
  "error": "validation_error",
  "message": "side: side must be 'buy', 'sell', or 'close'"
}

Error Response (queue full):

{
  "status": "error",
  "error": "queue_full",
  "message": "System at capacity, please retry in 30 seconds"
}

---

Signal Processing Errors

Rejection Reasons

Rejections occur before SignalBee attempts to execute on the exchange. Your signal was received but could not be processed due to your configuration.

Failure Reasons

Failures occur during execution when SignalBee encounters an error communicating with the exchange or processing your order.

---

Exchange Connection Errors

These errors occur when SignalBee cannot communicate with your exchange.

Authentication Errors

SignalBee IP Addresses

If your exchange requires IP whitelisting, add these IPs:

• Contact support for current IP addresses (these may change)
• Alternatively, disable IP restrictions on your exchange API key

Connection Errors

---

Order Execution Errors

These errors are returned by the exchange when your order cannot be placed.

Balance and Size Errors

Symbol and Market Errors

Price Errors (for limit orders)

Other Order Errors

---

Perpetual/Futures Specific Errors

These errors only apply to perpetual futures trading (not spot trading).

Margin Errors

Position Errors

---

HTTP Status Codes

Quick reference for HTTP response codes.

---

Troubleshooting Flowchart

Use this decision tree to diagnose issues:

Signal not executing?
│
├─ Check SignalBee Signal History page
│  │
│  ├─ Signal received?
│  │  │
│  │  ├─ Status: "success" → Order executed! Check Order History
│  │  │
│  │  ├─ Status: "pending" → Order accepted by the exchange, waiting to fill
│  │  │  (e.g. a resting limit order). Check Order History or the exchange's
│  │  │  open orders — no action needed unless it never fills.
│  │  │
│  │  ├─ Status: "rejected" → Check the rejection reason:
│  │  │  ├─ duplicate_signal → Wait 5 minutes before retrying
│  │  │  ├─ webhook_disabled → Enable webhook in SignalBee
│  │  │  ├─ trading_disabled → Enable trading for exchange
│  │  │  ├─ pair_not_whitelisted → Add pair to whitelist
│  │  │  └─ order_exceeds_max_size → Reduce quantity
│  │  │
│  │  └─ Status: "failed" → Check the failure reason:
│  │     ├─ invalid_credentials → Re-enter API key/secret
│  │     ├─ insufficient_balance → Deposit funds
│  │     ├─ rate_limit_exceeded → Wait and reduce frequency
│  │     ├─ exchange_unavailable → Check exchange status
│  │     └─ order_execution_failed → See exchange error
│  │
│  └─ No signal received?
│     │
│     ├─ Check TradingView alert
│     │  ├─ Alert fired? → Check webhook URL format
│     │  └─ Alert not fired? → Check alert condition
│     │
│     └─ Check webhook URL
│        ├─ Correct user ID? → Should be UUID from SignalBee
│        └─ Using HTTPS? → Required for webhooks
│
└─ Order placed but not filled?
   │
   ├─ Market order → Should fill instantly; check exchange
   └─ Limit order → May be waiting; check open orders

---

Exchange-Specific Error Mappings

SignalBee normalizes exchange errors into common types. Below are mappings for all 32 supported exchanges.

Note: Errors that don't match any known mapping are classified as unknown. If you encounter an unknown error, check the exchange's raw error message in the order details for more information.

Spot Exchanges

Binance

Bybit

Kraken

OKX

KuCoin

Coinbase

Gate.io

Bitget

BingX

HTX (Huobi)

Bitfinex

Bitstamp

MEXC

Binance-style negative codes (-1021, -1022, -2015, -1003, -2010, -1121, -1100 to -1117) are still mapped as defensive fallbacks, but the real spot v3 API returns the codes above.

Bitmart

Bitrue

WhiteBIT

XT.com

XT spot returns a string message code (mc), not a numeric one — the numeric rc is only 0 (success) / 1 (failure). Errors are mapped from mc.

LBank

BTC Markets

NDAX

NDAX (AlphaPoint) reports failures as HTTP 200 responses with an errormsg string, so errors are mapped by message rather than numeric code:

A bare HTTP 404 on a private endpoint also maps to invalid_credentials — NDAX hides private routes from sessions with bad credentials.

HashKey

Foxbit

Hyperliquid

Hyperliquid uses message-based error detection:

---

Perpetual/Futures Exchanges

Perpetual exchanges have additional error types for margin and position management.

Binance Perpetual

Bybit Perpetual

OKX Perpetual

KuCoin Perpetual

Gate.io Perpetual

Bitget Perpetual

Hyperliquid Perpetual

---

Getting Help

If you can't resolve your issue using this reference:

1. Gather Information

Before contacting support, collect:

• Signal ID or Order ID (from SignalBee history)
• Exact error message (copy the full text)
• Timestamp (when the error occurred)
• Steps to reproduce (what triggered the error)
• Exchange (which exchange you're using)
• Screenshot (of the error in SignalBee UI)

2. Check External Resources

• Exchange Status: Check your exchange's status page for outages
• TradingView Status: Verify TradingView alerts are working
• SignalBee Status: Check our status page for known issues

3. Contact Support

Email: support@signalbee.trade

Include all information from step 1 in your message. Do not include your API keys or secrets.

---

Related Documents

• Webhook Templates - Correct payload formats for all exchanges
• API Key Best Practices - Secure credential management
• Exchange Guides - Exchange-specific setup instructions