Register your game

Set up your project, callback, assets and permissions.

1. Pick the URLs

This series uses a static host page and a separate callback file. They share an origin; the exported game can live in a subfolder or on another HTTPS host.

Game host:  https://your-game.example/
Callback:   https://your-game.example/callback.html
Export:     https://your-export.example/game/index.html

Replace these example domains with yours. The callback must be an exact HTTPS URL, with no query, fragment or custom port. Preserve the registered path and extension: a redirect from callback.html to callback changes the URL being validated.

2. Submit an application

Open the developer console, verify your email, and supply your game title, description, launch URL, support/privacy links and callback. Upload your own square static PNG icon: 128–512 pixels, RGB/RGBA, at most 200 KB. weBump hosts the reviewed icon so it can appear in the app without an app update.

Request both authorization_code and device_code for this walkthrough. The first handles approval on the same iPhone; the second handles a game on a computer with approval on the player’s iPhone.

3. Request the permissions you use

Permission	How this demo uses it
`profile.basic`	Player name and color for the car and nameplate.
`game.state`	Private progress and replay saves.
`visitors.receive`	Eligible bump visitors for the rival roster.
`game.capsule`	Reviewed racing values carried with visitor cards.
`game.showcase`	Reviewed values on the player’s public game card.
`game.shared`	One explicitly published replay, delivered through a visitor reference.

For the unchanged demo, use its data definition in the application. Private save keys do not require a fixed high-score schema; public fields and selected shared data do need reviewed definitions. Change those definitions to suit your own game before requesting review.

4. Verify the domain and finish review

After submitting, copy the exact TXT name and value shown in the console to your DNS provider. The name is _webump.<callback-host>; some providers append your domain automatically. Wait for it to resolve, then choose Verify domain in the console. Don’t invent the TXT value.

If the reviewer requests changes, read their note, edit the application and resubmit. After approval, copy the public client ID. Changes to approved scopes, callbacks, schemas or connection methods go through project review.

Checkpoint

Your project is approved, the callback domain is verified, and both connection methods and the requested scopes appear in its settings. The client ID is public configuration. There is no shared API key to hide in Godot or email to players.