The Nestri REST API lets you build on top of Nestri’s cloud gaming infrastructure. Every endpoint returns JSON, all responses share a consistent envelope shape, and errors follow a single predictable structure. The API is versioned atDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/nestrilabs/nestri/llms.txt
Use this file to discover all available pages before exploring further.
0.0.1 and served over HTTPS.
Base URLs
Two environments are available. Use the production URL for live integrations and the sandbox URL when testing.| Environment | Base URL |
|---|---|
| Production | https://api.nestri.io |
| Sandbox | https://api.dev.nestri.io |
Every response includes a
Cache-Control: no-store header. Do not cache API responses on the client side.Response envelope
All successful responses wrap their payload in a top-leveldata key.
data as an array:
Error responses
When a request fails, the API returns a JSON object with three fields.High-level error category. One of
authentication, not_found, validation, or internal.Machine-readable error code for programmatic handling (e.g.
UNAUTHORIZED, RESOURCE_NOT_FOUND, INVALID_PARAMETER, INTERNAL_ERROR).Human-readable explanation of what went wrong.
HTTP status codes
| Status | Meaning |
|---|---|
200 | Request succeeded |
400 | Bad request — validation or missing parameters |
401 | Unauthenticated — missing or invalid token |
404 | Resource not found |
429 | Rate limit exceeded |
500 | Internal server error |
Endpoints
Account
Fetch the current user’s profile and linked Steam accounts.
Games
List your game library or look up a specific game by ID.
Steam
List linked Steam accounts and trigger the OpenID login flow.
Friends
List or look up friends by their Steam ID.