Fireblocks Rate Limits
Fireblocks REST API rate limits. Limits apply per workspace and per API user. Bursts return HTTP 429 with a Retry-After header. Read-heavy and pagination endpoints are subject to lower per-second ceilings; transaction-creation endpoints are protected by additional concurrency controls. Workspace tier (Essentials, Pro, Enterprise, Enterprise+) influences the negotiated ceilings.
Fireblocks Rate Limits is the machine-readable rate-limit profile for Fireblocks on the APIs.io network, in the API Commons Rate Limits shape.
It captures 6 rate-limit definitions, across the Essentials, Pro, Enterprise, Enterprise+, and all tiers.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes response codes documented for throttled and quotaExceeded.
Tagged areas include Rate Limiting, Quotas, Custody, and Wallets.
limitremainingresetretryAfter
generated, dated 2026-05-25.
Limits
Sources
- https://developers.fireblocks.com/reference/api-overview
- https://developers.fireblocks.com/docs/quickstart
- https://www.fireblocks.com/pricing
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.