Rate Limit

Learn about the API rate limits for the Mobee Open API.

Rate Limits

To ensure fair usage and maintain platform stability, the Mobee Open API applies rate limiting to all authenticated API requests.

Rate Limit

By default, each authenticated user is limited to:

10 requests per second, per endpoint

The limit is enforced per user and per endpoint path. The rate limiter keys its counter on your user ID combined with the request path (for example, 123456:/v1/orders), so each endpoint has its own independent budget rather than sharing a single global one.

The rate limiter is backed by Redis and uses a fixed window. Both the rate (10) and the window duration (expires_in, defaults to 1 second) are configurable on the server side.

Exceeding the Rate Limit

If the rate limit is exceeded, the API returns:

HTTP

HTTP/1.1 429 Too Many Requests

Clients receiving a 429 Too Many Requests response should wait before retrying their request. Consider implementing an exponential backoff or retry strategy in your application, and respect the Retry-After header (see below).

Example response:

HTTP

HTTP/1.1 429 Too Many Requests
Content-Type: application/json
Retry-After: 1

{
  "error": "Too Many Requests"
}

Rate Limit Headers

The API exposes the following rate limit headers:

Header	Description	When
X-RateLimit-Limit	The maximum number of requests allowed in the current window.	On every response
X-RateLimit-Remaining	The number of requests remaining in the current window.	On every response
X-RateLimit-Reset	Seconds until the current window resets.	On every response
Retry-After	Seconds to wait before retrying.	Only on 429 responses

Best Practices

To avoid hitting rate limits:

• Cache responses whenever possible.
• Avoid sending unnecessary repeated requests.
• Implement retry logic with exponential backoff when receiving a 429 Too Many Requests response, and honor the Retry-After header.
• Batch requests where applicable.

Related Documentation

• Authentication
• API Reference