POST
Create a project

Authorizations

Authorization
string
header
required

Developer session token from POST /v1/auth/login or POST /v1/auth/register. Valid 7 days.

Authenticates the developer control plane. It also reaches the server and build endpoints, which a dashboard has to drive and which no session can otherwise call: an API key's value is returned once, at mint, so nothing can read back a key for an existing project. On those endpoints a session names its project with project_id, or is resolved from the resource it addresses, and is always checked against the account that owns it.

It reaches no player-facing game endpoint.

Body

application/json

Creates a project. A sk_live_ and ck_live_ key pair is generated with it; retrieve them from GET /v1/projects/{project_id}/keys, or mint more with POST.

name
string
required
Example:

"My Game"

slug
string

Optional. Derived from name when omitted. Rejected with PROJECT_SLUG_TAKEN (7003) if already in use.

Pattern: ^[a-z0-9-]{1,64}$
Example:

"my-game"

Response

Project created.

A project owns builds, servers, queues, lobbies and its own pair of API keys. Usage is tracked per project and billed to the owning account.

project_id
string
required
Example:

"proj_abc123"

account_id
string
required
Example:

"acc_abc123"

name
string
required
Example:

"My Game"

slug
string
required

URL-safe identifier, unique across all accounts.

Pattern: ^[a-z0-9-]{1,64}$
Example:

"my-game"

created_at
string<date-time>
required
updated_at
string<date-time>
required