OAuth Authorization URL Builder
Build an OAuth 2.0 authorization URL: response type, client ID, redirect URI, scope, state and an optional PKCE challenge.
What the OAuth Authorization URL Builder does
response_type=code is fixed, because the implicit flow is deprecated and this page will not build it. Scope is sent as one space-separated string, which the encoder turns into + or %20 as the URL requires.
A challenge adds code_challenge and code_challenge_method=S256 together; the page never writes one without the other.
This builds the request URL, not the flow. There is no state generation, no token exchange and no discovery: the endpoint, client ID and redirect URI are yours, and a mismatch with what the provider registered is an error it will report.
How to use it
Set the Authorization endpoint, Client ID, Redirect URI, Scope, State and optionally a PKCE challenge, then press Run.
Read the Authorization URL below and open it in a browser, or copy it into a client.
Check the Authorization URL redirect_uri value — it must match one registered with the provider character for character.
Worked example
Input:
Output:
https://auth.example.com/authorize?response_type=code&client_id=abc&redirect_uri=https%3A%2F%2Fapp.example.com%2Fcb&scope=openid+profile&state=xyz
Why it runs in your browser
The result is produced on this page with JavaScript, so it works offline after the page loads and nothing you enter is sent anywhere.
The URL a browser is sent to for an authorization code: the response type, your client ID, the redirect URI, the scope, the state and — when you have one — the PKCE challenge.
The URL is built by the platform's URL parser, so the redirect URI and the scope are percent-encoded correctly rather than concatenated.
What it does, and what it does not
`response_type=code` is fixed, because the implicit flow is deprecated and this page will not build it. Scope is sent as one space-separated string, which the encoder turns into `+` or `%20` as the URL requires.
A challenge adds `code_challenge` and `code_challenge_method=S256` together; the page never writes one without the other.
This builds the request URL, not the flow. There is no state generation, no token exchange and no discovery: the endpoint, client ID and redirect URI are yours, and a mismatch with what the provider registered is an error it will report.
How to use OAuth Authorization URL Builder
Set the Authorization endpoint, Client ID, Redirect URI, Scope, State and optionally a PKCE challenge, then press Run.
Read the Authorization URL below and open it in a browser, or copy it into a client.
Check the Authorization URL redirect_uri value — it must match one registered with the provider character for character.
What to Expect
Best for
- Testing an authorization request by hand
- Checking the exact URL a client will send
Not ideal for
- Generating state or a PKCE pair, which are their own pages
- The client-credentials flow, which has no authorization URL
What this tool keeps
- Every parameter percent-encoded once
- The challenge method tied to the challenge
What may need cleanup
- Generate a state yourself and compare it on return
- Register the redirect URI with the provider first
Common errors
- The page refuses it: the base URL must be http or https
Example use cases
- Debugging a redirect_uri mismatch
- Preparing a manual authorization request
Sample input
Authorization settings:
Sample output
Authorization URL: https://auth.example.com/authorize?response_type=code&client_id=abc&redirect_uri=https%3A%2F%2Fapp.example.com%2Fcb&scope=openid+profile&state=xyz …
Who this is for
- Developers integrating an OAuth provider
- Anyone testing a login flow by hand
Frequently asked questions
Why is response_type fixed to code?
The implicit flow returns a token in the fragment, which is deprecated for good reasons. This page builds the authorization-code request only.
Can I use it without PKCE?
Yes — leave the challenge empty. Public clients should use PKCE, and the generator page produces the pair.
Does it validate my client ID?
Only that it is present. Whether it exists is the provider's answer, which arrives after the redirect.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.