Base URL
API Documentation
- ReDoc:
https://core.hyperx.dev/reference - Swagger UI:
https://core.hyperx.dev/swagger - OpenAPI JSON:
https://core.hyperx.dev/openapi.json
snake_case.
ReDoc and Swagger UI group endpoints by OpenAPI tags in this order: Project and Utilities, Users and Sessions, Data, Content, LiveOps, Purchases, Social, Support, Realtime.
Common Headers
| Header | Required | Description |
|---|---|---|
x-project-code | Yes for most project APIs | Project code from Console. |
Authorization: Bearer <access_token> | Yes for authenticated APIs | Access token returned after login. |
Content-Type: application/json | Yes when sending a JSON body | Marks the request body as JSON. |
x-trace-id | No | ID used to trace a flow across multiple requests. |
x-request-id | No | ID for one request. |
Call Examples
Check that a project code is available./v1/users/session/refresh to issue a new session.
API Areas
| Area | Main Features |
|---|---|
| Project and Utilities | Project lookup, server time, supported countries, region detection |
| Users | Guest/custom/social login, refresh, logout, current user, characters, account deletion/recovery |
| Data | Shared data, user data, character data |
| Content | Public Storage, game configs, probability tables |
| LiveOps | Rankings, coupons, game logs, operation content, push devices |
| Purchases | Store purchase validation, purchase history, refund/cancel webhooks |
| Social | Search, random lookup, friends, mail, messages, guilds, guild invites/goods, notifications |
| Support | Ticket creation, current-user ticket list/detail, replies, attachment metadata |
| Realtime | Notification stream, chat channels, messages, acknowledgements, reports |
Error Shape
Errors return JSON. Branch on the HTTP status andcode; include trace_id and request_id when contacting support or checking logs.