weBumpdevelopers
THE WEBUMP PLATFORM · PREVIEW

Little encounters.
New possibilities.

Bring the people players pass into the apps and worlds you build. A profile, a shared game stat, a new visitor—with permission at every step.

Free to explore. No account needed for the sandbox. The demo is a real game on this API, open source.
Pip: Collecting little adventures. 12 interactions.
Your test player
Mochi: Always room for one more friend. 9 interactions.
A friendly visitor
Fern: Taking the scenic route. 4 interactions.
Just passing by
Real weBump cards. Fictional people.
01 Profiles with permission02 Small game saves03 Visitors from local history
A PLACE TO EXPERIMENT

Meet your first visitors.

Run real HTTP requests against an isolated sandbox. Every profile here is fictional.

● SYNTHETIC DATA
GET /v1/meREADY
// Your first request is one click away.
// No sign-up. No real player data.
Use this sandbox from your own code

Start a session to get a temporary sandbox-only token. Only copy it into test code.

Run a request to generate your example.
FROM PLAYGROUND TO PROJECT

A small API.
Room to play.

Build an app or game on any platform using the HTTPS API, a public client ID, and either callback-based OAuth with PKCE or explicit device approval. Players approve connections in weBump; your app stores its own delegated tokens securely.

01

Connect a player

Open /oauth/authorize in the system browser with S256 PKCE and a random state. Exchange the one-time callback code at /oauth/token.

02

Give their game a memory

Read /v1/me/state. Save a named value with PUT /v1/me/state/{key} and the latest ETag in If-Match. Keep a local save too.

03

Welcome a visitor

Read /v1/me/visitors: the people your player bumped, including verifiable recent history synced by weBump, once unwrapped and their reveal delay passed. Only their approved profile and game fields come through.

Sandbox coverage and live API limits

The sandbox implements profile reads, permissions, named game state, a simulated handoff, withdrawn-consent errors, and game-data deletion. It skips OAuth and encounter timing. Live connections require an approved project, player consent in the compatible weBump iPhone app, a verified HTTPS callback, and PKCE. Apple identifiers are not required for your integration. A dedicated desktop pairing flow is not available yet. Live handoffs use begin/redeem instead of the sandbox-only simulate action.

Private game state: 16 keys / 16 KiB. Shared capsules: 2 KiB with reviewed integer, boolean, or enum fields. Selected shared game data: 16 KiB of reviewed nested JSON, separate player opt-in, and authorized visitor access. Never store secrets or personal contact details. The platform is a preview, and deleted weBump installations lose their game data.