HashiCorp Nomad · Rate Limits

Nomad Rate Limits

The Nomad HTTP API does not enforce HTTP-level rate limits in the open-source distribution. Throughput is bound by Nomad server capacity (Raft commit, scheduler workers, RPC concurrency) and client-side ACL token limits. Nomad supports blocking queries and long-poll consistency modes that control how clients consume the API. Rate-limit-style protections are configured operator-side via ACL token hierarchies, namespaces, and Sentinel policies (Enterprise).

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

It captures 4 rate-limit definitions, measuring varies, long-poll-duration, and per_page.

The profile also includes 5 backoff/retry policies defined and response codes documented for badRequest, forbidden, notFound, and serverError.

Tagged areas include Rate Limiting, Workload Orchestration, and DevOps.

4 Limits
Rate LimitingWorkload OrchestrationDevOps

Limits

Nomad HTTP API server
varies
bound by server CPU, memory, Raft commit rate
No per-second HTTP rate limit enforced; throughput is implementation-bounded.
Blocking queries per-request
long-poll-duration
5 minutes (default wait)
Clients can long-poll via index= and wait= parameters; `wait` defaults to 5 minutes, capped at 10 minutes.
Pagination per-request
per_page
100 (default)
Use `next_token` for cursor-based pagination on list endpoints.
ACL token enforcement token
varies
token-policy-bound
ACL policies bound which endpoints / namespaces / nodes a token can reach.

Policies

Blocking queries / consistency modes
Use index= and wait= parameters for long-poll behavior; choose `stale` consistency for reads to spread load across followers and reduce leader pressure.
Pagination
Use `next_token` cursor pagination; do not enumerate all jobs / allocations in a single request.
ACL token scoping
Issue narrowly scoped ACL tokens per integration; revoke unused tokens promptly.
Sentinel governance (Enterprise)
In Enterprise, Sentinel policies can rate-limit operations like job submissions per namespace.
Namespaces (Enterprise)
Use namespaces to isolate teams and prevent noisy-neighbor scheduler pressure.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/nomad-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.