Nakama Authentication API
Authenticate users and issue or refresh session tokens.
Nakama Authentication API is one of 11 APIs that Nakama publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 4 operations across 4 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 2.0.
Requests are made against a single base URL, http://127.0.0.1:7350.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Nakama Authentication API declares
2 security schemes
for authenticating requests.
It accepts HTTP basic authentication (BasicAuth).
It accepts HTTP bearer tokens (JWT) (BearerAuth).
By default, every request must be authenticated.
BasicAuth— HTTP Basic auth using the server key as the username and an empty password. Guards the authenticate endpoints.BearerAuth— The JWT session token returned by an authenticate call, sent as Authorization: Bearer .
Paths & Operations 4
Across 4 paths, the API surfaces 4 operations — 4 POST. Each is listed below with its method, path, parameters, and response codes.
Authenticate users and issue or refresh session tokens.
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are AuthenticateDeviceRequest (3 properties), AuthenticateEmailRequest (3 properties), AuthenticateCustomRequest (3 properties), AccountEmail (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Nakama 10
Other APIs Nakama publishes across the network.
This is an independent, third-party profile of Nakama Authentication API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.