Documentation
Everything a studio needs to put its game on GreenMind Publishing, from the first server key to the full API.
Start here
Concepts
ConceptsOrgs, moving projects between them, plans and licences, members and roles, projects, environments and their app keys, and the services a project switches on.AuthenticationServer keys for your game servers, access and refresh tokens for your players, and how to keep each safe.Environments and releasesDeveloping against test, shipping against production, adding environments, and moving changes between them.
Services
PlayersSigning players in from your own server or with Epic Online Services, identities, and display names.SessionsLobbies your players create, join and ready up in, and how your game server reports the match that follows.Config and flagsEditing config values and feature flags per environment, and reading them from your game.Player savesSaving JSON per player in slots you name, writing without losing another write, and the size limits.Crash reportsPointing Unreal's crash reporter at your environment, and reading its crashes grouped into bugs.CommerceSelling through Steam with your own keys: products, the purchase flow, entitlements, and the currency your server collects.Game servicesRealms, inventories, currencies with a ledger, items, cards and decks, skill trees, unlocks and stats: defined in the console, granted by your server.WebhooksEvents sent to your server as they happen: the events and their payloads, verifying signatures in Node and C++, retries, and failing endpoints.Other servicesLegal documents, tours, blog, support, staff, Sign in with GreenMind and analytics: what each does and how your game reaches it.Custom dashboardsYour own dashboard for a project, hosted by us: uploading a static site, publishing and rolling back, signing your team in with GreenMind, and what it may call.GmCommonLicensing our Unreal Engine plugin: binary and source tiers, online activation per machine, and downloads.
Reference
API referenceEvery platform API route with its credential, service, request fields, limits and responses, every error code, and the OpenAPI document.API explorerEvery platform API route read from its OpenAPI document, with its parameters, body and errors, and a panel that sends it with your server key or a test player.VersioningWhat may change within an API version, what never will, and how a route is deprecated before it goes.ChangelogWhat has changed in the platform API, newest first.