Project BlueSphere API Overview

Use the Project BlueSphere public API to exchange a BlueSphere login token for an auth code, then verify that auth code when an integration needs the current user profile.

Base URL

Production requests are served from:

https://prod.bluesphere.live

All requests documented here use Content-Type: application/json.

Authentication flow

  1. Send a BlueSphere login token, console identifier, and game string to POST /api/loginAuth.
  2. Store the returned authCode for authenticated API calls and the udpToken for UDP presence relay heartbeats.
  3. Send the authCode to POST /api/verify when an integration needs to confirm the token and retrieve user data.
  4. Send UDP heartbeat packets with the udpToken to keep the user's presence online and publish current game status.

The auth code is a base64url-encoded ECDSA-signed value generated by the backend. It expires after 24 hours and the current stored auth code is replaced when the user logs in again.

About BlueSphere

BlueSphere is a replacement PSN-style backend for PS4 and PS5 game integrations. It provides account services, presence, and web API endpoints that game clients can use for login, authenticated user data, online status, and game-facing service calls.

Public endpoints

MethodEndpointPurpose
POST/api/loginAuthValidates a BlueSphere login token and returns authCode, udpToken, accountId, and onlineId.
POST/api/verifyValidates an authCode and returns user data for the authenticated account.
UDP:8081Accepts heartbeat packets that update presence and current game state.

Was this page helpful?