Rate Limits

How DFNS rate limits the API: what the limit is measured against, the response headers that report your usage, and where to find the request-per-minute quota for your plan.

DFNS caps how many API requests an organization can make per minute. This keeps the platform stable and usage fair across all organizations.

How the limit is measured

• The limit applies per organization, across every application and service account it owns — not per API key or per endpoint.
• Requests are counted over a 60-second window. Exceeding the limit returns 429 Too Many Requests until the window resets.

Rate-limited responses carry headers describing your current usage:

Header	Meaning
X-RateLimit-Limit	Your maximum requests per minute.
X-RateLimit-Remaining	Requests left in the current window.
X-RateLimit-Reset	Unix time (seconds) when the window resets.
Retry-After	On a 429, the number of seconds to wait before retrying.

Back off using Retry-After (or X-RateLimit-Reset) rather than retrying immediately. See handling 429 responses for the recommended retry strategy.

Your quota

The request-per-minute limit depends on your plan. See DFNS pricing for the quota at each tier.

Need a higher limit? Contact our .