Rate Limits

Understanding and working within TradeStaq's API rate limits.

Overview

Rate limits protect the platform and ensure fair access for all users. Different endpoints have different limits based on their resource requirements.

Webhook Rate Limits

Per-Webhook Limits

What This Means

Rate Limit Headers

Responses include rate limit information:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 45
X-RateLimit-Reset: 1704067260

Rate Limit Response

When exceeded:

{
  "success": false,
  "error": "Rate limit exceeded",
  "code": "RATE_LIMITED",
  "retryAfter": 15
}

HTTP Status: 429 Too Many Requests

Exchange API Limits

Each exchange has its own rate limits that TradeStaq respects:

Binance

ByBit

OKX

Subscription Tier Limits

Feature Limits by Tier

Concurrent Limits

Handling Rate Limits

Retry Strategy

When you receive a 429 response:

import time
import requests

def send_signal_with_retry(url, payload, max_retries=3):
    for attempt in range(max_retries):
        response = requests.post(url, json=payload)

        if response.status_code == 429:
            retry_after = response.json().get('retryAfter', 5)
            time.sleep(retry_after)
            continue

        return response

    raise Exception("Max retries exceeded")

Exponential Backoff

For better retry handling:

import time
import random

def exponential_backoff(attempt, base_delay=1, max_delay=60):
    delay = min(base_delay * (2 ** attempt), max_delay)
    jitter = random.uniform(0, delay * 0.1)
    return delay + jitter

# Usage
for attempt in range(5):
    response = requests.post(url, json=payload)
    if response.status_code != 429:
        break
    time.sleep(exponential_backoff(attempt))

Rate Limit Best Practices

TradingView Considerations

TradingView Alert Limits

TradingView has its own limits:

Avoiding TradingView Issues

Monitoring Your Usage

Dashboard Metrics

In your TradeStaq dashboard, monitor:

Webhook Health Indicators

Common Issues

"Rate Limit Exceeded" Errors

Causes:

• Too many signals in short period
• Strategy generating excessive signals
• Multiple sources sending to same webhook

Solutions:

1. Add delays between signals
2. Review strategy logic
3. Use separate bots for different sources

Signals Being Dropped

Causes:

• Hitting burst limit
• Exchange rate limits
• Network issues

Solutions:

1. Implement queuing
2. Add retry logic
3. Check exchange status

Slow Execution

Causes:

• Near rate limits
• Exchange congestion
• High system load

Solutions:

1. Reduce signal frequency
2. Upgrade tier for higher limits
3. Try different times

Optimization Tips

For High-Frequency Strategies

For Multiple Bots

Limits by Endpoint

Quick Reference

Getting Higher Limits

Upgrade Options

Enterprise Options

For limits beyond Whale tier:

• Contact hello@tradestaq.com
• Describe your use case
• Custom limits may be available

Next Steps

• Webhook API - Webhook reference
• Authentication - Security guide
• Troubleshooting - Error resolution