Build

Rate Limits

Understand rate limiting in the Lev API, including per-endpoint limits and how to handle 429 responses.

Updated March 2026

Overview

Rate limits are applied per account and measured in requests per minute. When you exceed a limit, the API returns 429 Too Many Requests.

Your current rate limits are visible in the GET /me response under platform.rate_limits.

Endpoint Type	Limit
Read endpoints (`GET`)	200 requests/minute
Write endpoints (`POST`, `PATCH`, `DELETE`)	30 requests/minute
Authentication (`POST /auth/validate-api-key`)	10 requests/minute

These are default values. Your specific limits may differ based on your subscription tier and can be checked via GET /me.

When rate limited, the API returns:

{
  "request_id": "...",
  "error": {
    "code": "RATE_LIMITED",
    "message": "Rate limit exceeded. Retry after 30 seconds."
  }
}

Best practices:

Implement exponential backoff — wait progressively longer between retries
Use bulk endpoints where available instead of many individual requests
Cache responses for data that doesn't change frequently (e.g., market data, asset types)
Use sparse fieldsets to reduce payload sizes and improve response times
Monitor your usage via the GET /me endpoint to stay within limits