Tools / Request playground
See the request
before you send it.
Turn your app’s settings into a real authorization URL. Inspect the PKCE values and copy the request to understand each part of the flow. Choose required, optional and conditional scopes to try the consent behavior.
01 Your app
Valid URL — if it isn’t saved yet, register it below.
02 Scopes
Selected identity scopes go in mandatory scope. Use the fields below to choose how API access and optional identity data are requested.
Separate scopes with spaces and put each scope in one list only. Replace the example app AUID with the permission’s declaration owner. Availability is checked during authorization.
03 Fresh values
generating…Live request
Live requestGenerating fresh values…
Nothing here is sent anywhere until you press the button.
What happens after authorization?
After account selection, AXUS ID checks access and asks for any needed consent. Missing mandatory permissions return access_denied with state and no code. Optional scopes can be turned off; unavailable optional and conditional permissions are omitted. Held conditional permissions must be approved to continue.
On success, AXUS ID redirects to your registered callback with a code and state. This playground keeps its verifier in this page only; it does not create a transaction in your app. Your normal callback should reject an attempt it did not initiate. To complete a real integration, generate and store the transaction in your app.
After exchanging the code, check the token response’s scope for the approved OIDC and AXUS scopes before enabling features. See the permission flow walkthrough.