Authorization & tokens
Authorize in the browser
Begin browser authorization from a valid pushed authorization request. Confidential application requests can start while signed out or with an expired browser session; EFM redirects to its fixed login/consent origin, then requires an authenticated user in the owning account before context or approval. For MCP, the human follows the emailed link and a single Continue chooses normal signup or sign-in. New accounts reuse the verified mailbox, enter and confirm their password in the first-party signup form, then complete business details and affirmative terms/agency consent. Password confirmation is a browser check, not an OAuth/MCP request field. Fresh completed browser authentication can satisfy identity confirmation; older sessions use the normal verification flow. The client owns its callback completion page.
/oauth/authorize- Authentication
- Browser sign-in and consent
- Required scopes
- See authentication requirements
- Idempotency key
- Not required
How to use this endpoint
Confidential external API clients supply client_id and the one-time request_uri from PAR. Public MCP clients may instead provide a complete direct authorization-code request for the exact MCP resource, with S256 PKCE. Do not mix a pushed request with overriding authorization parameters. The browser proceeds to sign-in and explicit consent; no token is issued by opening this URL.
If first-party signup verification is cancelled, the customer can re-enter the original password and resume the same unfinished account with the same name and email. An unverified text-message phone can be corrected with that password proof; an already verified phone cannot. Correction invalidates prior signup verification attempts and still requires a fresh code. Choosing another unverified setup method does not bypass SMS verification or remove an already verified authenticator. Signup resumption does not issue an OAuth token or approve the integration; the original authorization and consent steps still apply. During migrated-account browser verification, a sole email/SMS method sends automatically; with multiple methods, clicking the chosen tile sends the code. The same tile handles resending after the cooldown.
curl --request GET '<origin from OAuth metadata>/oauth/authorize' \
--get \
--data-urlencode 'client_id=<client_id>' \
--data-urlencode 'request_uri=<request_uri>'Use the exact endpoint URL from your environment's metadata. Confidential client examples use client_secret_basic; public MCP clients use client_id without a secret.
Request fields
9 fieldsquery.client_idSee descriptionSee description
registered client ID
query.request_uriSee descriptionSee description
Required for pushed authorization; omit only for a supported complete direct public MCP request.
query.response_typeSee descriptionSee description
Direct public MCP flow only: code.
query.redirect_uriSee descriptionSee description
Direct public MCP flow only: exact registered return URI.
query.resourceSee descriptionSee description
Direct public MCP flow only: exact MCP resource URI.
query.scopeSee descriptionSee description
Direct public MCP flow only: requested permitted scopes.
query.stateSee descriptionSee description
Direct public MCP flow only: caller-generated state.
query.code_challengeSee descriptionSee description
Direct public MCP flow only: 43-character base64url SHA-256 challenge.
query.code_challenge_methodSee descriptionSee description
Direct public MCP flow only: S256.
curl --request GET '<origin from OAuth metadata>/oauth/authorize' \
--get \
--data-urlencode 'client_id=<client_id>' \
--data-urlencode 'request_uri=<request_uri>'Use the exact endpoint URL from your environment's metadata. Confidential client examples use client_secret_basic; public MCP clients use client_id without a secret.
Successful outcomes: redirect.
"Empty body; Location points to the first-party consent UI with only client_id and request_uri selectors."Authorization request accepted; the browser continues to sign-in and consent.
Errors to handle
Use the returned status and code to decide what to correct or retry.
- 400
invalid_request - 401
unauthorized - 503
temporarily_unavailable