Developer Resources

API Reference - NexusLaunch Docs

One Launcher. Infinite Worlds. Query game status, trigger launches, and sync cloud saves directly from your tools.

API Overview

The NexusLaunch REST API provides programmatic access to the launcher's core functionality. Built on a 99.9% uptime infrastructure, our v2.4 endpoints support up to 1,200 requests per minute per developer key. Whether you're building a companion app, a custom overlay, or a cross-platform save manager, the API handles JSON payloads with standard HTTP status codes and rate-limit headers.

Base URL: https://api.nexuslaunch.dev/v2. All responses return application/json. Timestamps follow ISO 8601 format. Paginated lists use cursor-based navigation with a default limit of 50 items per request. Error objects include a machine-readable error_code and a human-friendly message field.

Core Endpoints

GET /games/status

Retrieve real-time launch states for installed titles. Returns idle, running, updating, or crashed along with process IDs and memory footprint. Supports filtering by genre, publisher, or last_played date range.

POST /launch

Trigger a game launch with optional parameters like resolution, fullscreen_mode, and pre_launch_scripts. Accepts a game_id (UUID v4) and returns a session_token for tracking launch telemetry. Rate limited to 15 executions per minute.

PUT /cloud/save-sync

Push local save files to NexusVault storage. Requires base64-encoded payloads under 256MB. Automatically handles conflict resolution using timestamp-based versioning. Returns a sync_id and checksum for verification.

GET /community/leaderboards

Fetch ranked data for supported titles like Aetheria Online and Neon Drift 2. Supports sorting by score, region, or platform. Includes pagination cursors and raw JSON export options for third-party stat trackers.

Authentication & Security

Access the NexusLaunch API using OAuth 2.0 Bearer tokens. Developer accounts are provisioned through the NexusDev Portal at dev.nexuslaunch.dev. Each registered application receives a client_id and client_secret pair, which must never be exposed in client-side code.

Token acquisition follows the standard authorization code flow. Redirect URIs must use HTTPS and match your registered callback domains. Bearer tokens expire after 3600 seconds and require a refresh_token for silent renewal. All API requests must include the Authorization: Bearer header and a valid X-Nexus-App-ID header for routing. IP whitelisting and webhook signature verification are available for enterprise integrations.