BUILD SOMETHING REAL

Your developer console.

Verify your email, tell us about your app, and apply for live access.

Tell us about your app

We review what you’re building and the data it needs. Approval unlocks your project automatically. If we request changes, you’ll see our notes here and can edit and resubmit.

Your nameStudio / organizationApp nameWhat are you building for?What are you building, and how will it use weBump?HTTPS callback URLPrivacy policy URLGame launch URLGame icon (PNG)Square, 128–512 pixels, RGB or RGBA, up to 200 KB. Screened automatically for harmful content when you submit, then reviewed before publishing.Support URL

Your callback must use HTTPS on a public domain you control, with no query parameters, fragment (#), or custom port. Use a real callback handler, such as https://game.example/connect/callback. After submission, we give you a TXT record to add at _webump.<callback-domain>; DNS verification is required before approval. We append the OAuth result when the player returns. No Apple developer account is required.

Connection methodsRegistered callback + PKCEFor a website or app that receives an HTTPS callback. Polling never returns a code.Device connection (phone approval)For apps, websites, desktops and consoles. Display a matching code; the player explicitly approves that device. Public clients can be copied: this method does not prove software authenticity or restrict where the game runs. Requires review.

Requested permissions

Request only what your game needs. Approval permits your app to ask; each player still chooses whether to connect.

Basic profileRead the connected player’s display name and color. No email, location, or installation secret. Private game stateRead and write your game’s private JSON save for this player, including arrays and nested objects. Other games cannot read it. Visitor handoffsAsk the player to bring eligible visitors from their local weBump history into your game. Only cards allowed by each visitor’s privacy choices are returned. Shared game capsuleRead and write a small set of reviewed game values that can travel with visitor cards, such as a racer class or level. The player must separately enable sharing. Shared game dataPublish selected, reviewed JSON for this game’s authorized visitors to retrieve. Supports nested objects and arrays; never appears on weBump profiles. Requires a separate player opt-in. Also request Visitor handoffs to retrieve it. Showcase fieldsRead and write reviewed fields for your game’s public profile card. Everyone can see them when the player enables “Show on my profile.”

Shared field definitions (optional)

Declare only small game values for capsules and showcases. Use boolean, bounded integer, or an enum of bundled asset identifiers. These fields are reviewed with your application. For Shared game data, add a shared object containing your bounded JSON schema. Schema example and limits ↗

Data definition (JSON)

Example field: "level":{"label":"Level","type":"integer","min":0,"max":100}

I accept the developer agreement (September 10, 2026) and confirm that I control this app and its callback domain.

Your developer console.

Start with your email

Check your inbox

Tell us about your app