Skip to main content
The API enforces per-key and per-IP rate limits to ensure fair usage. Limits vary by API and endpoint sensitivity.

Instance API Limits

Instance API endpoints (Customers, Tokenization, Trading, etc.) apply layered rate limiting. A request that carries an API key counts against the API key limiter only, so the per-IP global limit never applies to it. The stricter limiters apply only to specific endpoint groups. When multiple limiters apply, the most restrictive active limit governs.

Response Headers

429 Response

MiCA Register API Limits

The MiCA Register API enforces separate per-key limits. MiCA rate limit headers use a different format:

Caching

Most read endpoints return Cache-Control headers. Respecting these headers reduces unnecessary requests against your quota.
Use the X-RateLimit-Remaining (or X-RateLimit-Remaining-Minute) header to implement client-side throttling before hitting the limit.