Hathora AuthV1 API
Player authentication - issue short-lived player tokens.
Hathora AuthV1 API is one of 11 APIs that Hathora publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include AuthV1. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 3 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version 3.0.
Requests are made against a single base URL, https://api.hathora.dev.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Hathora AuthV1 API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (hathoraDevToken).
It accepts HTTP bearer tokens (JWT) (playerAuth).
By default, every request must be authenticated.
hathoraDevToken— Organization developer/API token used for management endpoints (apps, builds, deployments, processes, rooms, logs, metrics, billing, tokens).playerAuth— Short-lived player token issued by the AuthV1 login endpoints, used by game clients for room and lobby operations.
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.
Player authentication - issue short-lived player tokens.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ApiError (1 property), PlayerTokenObject (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Hathora 10
Other APIs Hathora publishes across the network.