Hathora · Rate Limits

Hathora Rate Limits

The Hathora Cloud REST API is authenticated with an organization developer token (hathoraDevToken) for management endpoints and short-lived player tokens for room/lobby operations. Hathora did not publish fixed numeric request-per-minute limits on the management API; the practical constraints were resource quotas - concurrent running processes, rooms-per-process, and requested CPU/memory - governed by the account tier (Explore free tier vs. Pro vs. Enterprise). Standard HTTP 429 is returned when a client is throttled.

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

It captures 5 rate-limit definitions, measuring processes, rooms, resources, and requests.

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

Tagged areas include Game Servers, Multiplayer, Compute, Hosting, and Orchestration.

5 Limits Throttle: 429
Game ServersMultiplayerComputeHostingOrchestrationRate LimitingQuotasThrottling

Limits

Concurrent Processes application
processes
see provider documentation
Number of simultaneously running game server processes; capped on the Explore free tier, higher on Pro/Enterprise.
Rooms Per Process process
rooms
configured per deployment
Set via the deployment's roomsPerProcess; new rooms schedule onto processes with capacity.
Requested CPU / Memory deployment
resources
configured per deployment
Requested vCPU and memory (MB) per process are defined in the deployment config and bounded by tier.
Management API Requests account
requests
see provider documentation
No fixed public RPM published for the REST management endpoints; excessive requests may be throttled with 429.
Player Token Issuance application
requests
see provider documentation
AuthV1 login endpoints issue player tokens; abuse-level request rates may be throttled.

Policies

Tiered Quotas
Concurrency and resource ceilings raise from the Explore free tier to Pro and Enterprise agreements.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429 responses.

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/hathora-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 email required.

GitHub Google LinkedIn

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