Skip to main content
ELUUP AI enforces rate limits to ensure fair usage and platform stability. Limits vary by subscription plan and apply to REST API calls. Server-Sent Event (SSE) streams for signals do not count toward your REST rate limit.

Rate Limits by Plan

Upgrading your plan increases the limit immediately. Downgrades take effect at the next billing cycle.

Rate Limit Headers

Every REST API response includes headers that show your current usage. Inspect these to decide when to back off.

Example Response Headers

429 Rate Limited Response

When you exceed your limit, the API returns 429 with a JSON body and the same headers.

Best Practices

Cache Signals Locally

Store the latest signal data in your application state instead of polling on every UI refresh.

Use SSE for Real-Time

Subscribe to GET /signals/stream for live updates. SSE streams do not count toward REST rate limits.

Respect Headers

Read X-RateLimit-Remaining and pause requests before you hit zero.

Back Off on 429

Wait until X-RateLimit-Reset before retrying, or use exponential backoff with jitter.

Polling vs. Streaming Example

For production trading integrations, use the SSE signal stream to receive buy and sell signals in real time without consuming your REST quota.