Safe (Gnosis Safe) · Rate Limits

Gnosis Safe Rate Limits

Safe enforces per-plan rate limits on the Transaction Service API measured in requests per second (RPS) and total monthly API units (one unit = one HTTP request to any Safe Infrastructure endpoint). Unauthenticated callers are capped at 2 RPS and 5,000 monthly requests. Authenticated callers on the Builder free tier get 5 RPS and 50,000 monthly calls. Growth paid plan raises this to 15 RPS and 1M monthly calls. Scale raises it to 50 RPS and 3M monthly calls. Remaining quota is communicated via response headers on every call. When a plan's monthly quota is exhausted, further requests return HTTP 429. Custom plans above Scale thresholds are available via support@safe.global.

Gnosis Safe Rate Limits is the machine-readable rate-limit profile for Safe (Gnosis Safe) on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 8 rate-limit definitions, measuring requests_per_second and api_units.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, unauthorized, and serverError.

Tagged areas include Multisig, Smart Contract, Blockchain, DeFi, and Wallet.

8 Limits Throttle: 429
MultisigSmart ContractBlockchainDeFiWalletRate LimitingThrottling

Limits

Unauthenticated RPS global
requests_per_second · second
2
No API key required but strictly limited; intended for initial exploration only.
Unauthenticated Monthly Quota global
api_units · month
5000
Builder RPS api_key
requests_per_second · second
5
Builder Monthly Quota api_key
api_units · month
50000
Growth RPS api_key
requests_per_second · second
15
Growth Monthly Quota api_key
api_units · month
1000000
Scale RPS api_key
requests_per_second · second
50
Scale Monthly Quota api_key
api_units · month
3000000

Policies

429 Throttling
When the monthly quota cap or per-second rate limit is exceeded, the Safe Transaction Service returns HTTP 429 Too Many Requests. Clients should back off before retrying.
Quota Headers
Remaining monthly quota and current rate-limit status are communicated via response headers on every API call. Applications should inspect these headers to implement proactive throttling before hitting the hard cap.
JWT API Key
API keys are JWTs with configurable expiration. Separate keys are recommended per environment (development, staging, production) to enable fine-grained monitoring and revocation.
Backoff Strategy
Implement exponential backoff with jitter when receiving 429 or 5xx responses. Cache Safe and transaction data locally where possible to avoid redundant reads.
Webhook Rate Management
Webhook delivery is included with Growth (2 endpoints) and Scale (10 endpoints) plans. Webhook retry logic and backpressure are managed by Safe infrastructure; client webhook handlers should respond promptly (2xx) to avoid retry flooding.

Sources