- Nakama
- Getting Started+-
- Concepts+-
- Server Framework+-
- Client Libraries+-
- API+-
- Tutorials+-
- Guides+-
- Overview
- Concepts+-
- Overview
- Edgegap Integration
- GameLift Fleet Management
- Bucketed Leaderboards
- Custom Authentication with Third-Party Services
- Custom Leaderboards
- Creating an Economy
- Daily Rewards
- Initialize a New User
- Matchmaking Around Blocked Users
- Passive Multiplayer
- Tiered Leagues
- Creating a Lobby System
- Unread Chat Messages
- Server Framework+-
- Deployment+-
- Videos
- Sample Projects
- Hiro
- Concepts+-
- Unity+-
- Unreal+-
- C+++-
- Dart+-
- TypeScript+-
- Godot+-
- Python+-
- Server Framework+-
- Guides+-
- Sample Projects
- Satori
- Heroic Cloud
Console API
The Satori Console API provides server-side access to manage your Satori instance programmatically. This API is intended for server-to-server communication and administrative tasks.
Authentication #
To communicate with the Satori Console API you must use a Server Key (not an API Key, which is for client APIs).
Server Keys must be passed as the username in a HTTP Basic Authentication header, with an empty password:
Authorization: Basic <base64(server_key:)>
For example, if your server key is my_server_key_123, you would base64 encode my_server_key_123: (note the trailing colon for the empty password) and use it in the header:
| |
Server Keys are different from API Keys. API Keys are used by game clients to communicate with the Satori client API, while Server Keys are for server-to-server communication with the Console API.
