Dash · Rate Limits

Dash Rate Limits

The Dash Insight API and DAPI are open-source, self-hosted or community-operated services with no formally published rate limit policy. Public instances at insight.dash.org are operated on a best-effort basis by Dash Core Group; high-volume consumers are encouraged to run their own Insight node. The DAPI is decentralized — requests are routed through masternode quorums, so practical throughput is determined by the network topology rather than a single rate-limit gate. Self-hosted Insight instances can apply nginx or application-level throttling at the operator's discretion.

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

It captures 4 rate-limit definitions, measuring requests_per_period and concurrent_connections.

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

Tagged areas include Rate Limiting, Cryptocurrency, Dash, Blockchain, and Open Source.

4 Limits Throttle: 429
Rate LimitingCryptocurrencyDashBlockchainOpen Source

Limits

Insight REST API — public instance (insight.dash.org) IP
requests_per_period
unspecified (best-effort community instance)
No published numeric cap. High-volume integrations should self-host dashcore-node + insight-api. Install via npm on Ubuntu following docs.dash.org/en/stable/developers/insight.html.
Insight WebSocket — public instance connection
concurrent_connections
unspecified
socket.io rooms: inv, sync, and per-address rooms. Subscribe to tx, txlock, block, and status events. High-frequency consumers should run a local node.
Dash Platform DAPI — gRPC endpoints network
requests_per_period
decentralized (per-masternode quorum)
Requests are load-balanced across masternode quorums. No single-key or single-IP cap is published. Rate limiting is effectively enforced by the masternode set's aggregate capacity.
Testnet Insight API (testnet-insight.dash.org) IP
requests_per_period
unspecified (best-effort testnet instance)
Intended for development and testing only; may have lower availability than mainnet.

Policies

Self-hosting recommended for production
Dash Core Group recommends that production applications run their own dashcore-node + insight-api stack rather than relying on the community-operated public instance.
Use WebSocket for real-time data
Subscribe to socket.io events (block, tx, txlock) instead of polling REST endpoints to reduce load on shared infrastructure and achieve lower latency.
Testnet for integration testing
Use testnet-insight.dash.org and the Dash testnet DAPI seed nodes for all development and integration testing before targeting mainnet.
DAPI decentralized load balancing
The dapi-client SDK automatically discovers and rotates across masternode quorum members. Use the official SDK rather than hard-coding seed addresses.

Sources