How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Ready Player Me Auth API

Anonymous user creation, email-code login, token refresh, and avatar access tokens used by the Ready Player Me Avatar Creator and SDKs. Authentication runs through each application's per-studio subdomain. RETIRED: the public platform was shut down on 2026-01-31 following Netflix's December 2025 acquisition, and api.readyplayer.me no longer resolves — this entry is a historical record of the contract, not a callable API.

Ready Player Me Auth API is one of 3 APIs that Ready Player Me publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication, Identity, and User. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 5 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.readyplayer.me.

5 operations 5 paths 2 schemas 5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.readyplayer.me/
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Ready Player Me Auth API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-APP-ID (AppId). By default, every request must be authenticated.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 POST. Each is listed below with its method, path, parameters, and response codes.

Auth 5

User authentication and token management.

POST
/api/users
Create Anonymous User
createAnonymousUser → 201
POST
/api/auth/start
Start Login With Email Code
authStart body → 200
POST
/api/auth/login
Confirm Login Code
authLogin body → 200
POST
/api/auth/refresh
Refresh Auth Tokens
authRefresh body → 200
POST
/v1/auth/token
Get Avatar Token
getAvatarToken body → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are User (4 properties), AuthTokens (2 properties). Each schema is shown below with its type and property counts.

AuthTokens
object
2 properties
User
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ready-player-me-auth-api-openapi.yml Raw ↑

Other APIs Ready Player Me publishes across the network.

Ready Player Me Avatars API
Ready Player Me Assets API
Where this information came from

This is an independent, third-party profile of Ready Player Me Auth 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.