Rate Limiting

The Monotree Open API enforces 60 requests per minute per token by default. The limit is configurable per server — your account team can raise it for high-volume integrations.

Incoming webhooks share the same limit, applied per webhook URL.

Headers

Every response includes:

HeaderValue
X-RateLimit-LimitMaximum requests in the current window.
X-RateLimit-RemainingRequests remaining in the current window.
X-RateLimit-ResetUnix timestamp when the window resets.

When the limit is exceeded, the response is 429 Too Many Requests:

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

{ "message": "Too Many Attempts." }

Backoff strategy

  1. Check X-RateLimit-Remaining on every response and slow down before you hit 0.
  2. On 429, wait for the duration in Retry-After (seconds) before retrying.
  3. For burst traffic, batch requests — e.g. paginate with per_page=50 instead of per_page=10.