Sandbox playground

Drive the full OAuth 2.0 + PKCE flow end-to-end against a shared sandbox client. No keys required — tokens issued here carry env="sandbox" and expire in minutes.

Configure the flow

client_id: loading…
redirect_uri: https://phase2.ucap.africa/developers/sandbox/callback

Requested scopes

consumer.profile.readRead the consumer's profile, contacts, and addresses.consumer.profile.writeUpdate the consumer's profile, contacts, and addresses.consumer.documents.readList and download the consumer's documents.consumer.documents.writeUpload and delete the consumer's documents.consumer.grants.readList consent grants the consumer has issued.consumer.grants.revokeRevoke a consent grant the consumer has issued.consumer.history.readRead activity history for the consumer.consumer.notifications.readRead notifications addressed to the consumer.consumer.notifications.writeMark notifications as read for the consumer.consumer.consent.readInspect pending consent sessions for the consumer.consumer.consent.respondApprove or deny a pending consent session.

You'll be sent to /oauth/authorize, sign in, approve, and return here.

How this works

1. The page generates a PKCE verifier/challenge pair and redirects you to the authorize endpoint.

2. You sign in as a consumer (or create a test account) and approve the requested scopes.

3. The callback page exchanges the returned code for an access token using the verifier — and then calls /me/profile so you can see the wire response.