Optional acr_Optional audienceThe default audience to be used for requesting API access.
Optional connectionThe name of the connection configured for your application. If null, it will redirect to the Auth0 Login Page and show the Login Widget.
Optional display'page': displays the UI with a full page view'popup': displays the UI with a popup window'touch': displays the UI in a way that leverages a touch interface'wap': displays the UI with a "feature phone" type interfaceOptional experiment_Forces a specific Experiment Center variant for this /authorize request
instead of letting Auth0 assign one via its hash. Use together with
variation_id.
Pass per-call (on loginWithRedirect/loginWithPopup) rather than at
client construction time so the override does not bleed into silent
prompt=none token-renewal calls, where Experiment Center does not run.
Testing: drive from test automation (e.g. Cypress/Playwright) with IDs from a CI environment variable against a staging tenant. Do not hard-code this in shipped app code.
Production: pass the variant decision from a feature-flag tool (e.g. LaunchDarkly) that has already decided which variant the user should see for this request.
Optional id_Previously issued ID Token.
Optional invitationThe Id of an invitation to accept. This is available from the user invitation URL that is given when participating in a user invitation flow.
Optional login_The user's email address or other identifier. When your app knows which user is trying to authenticate, you can provide this parameter to pre-fill the email box or select the right session for sign-in.
This currently only affects the classic Lock experience.
Optional max_Maximum allowable elapsed time (in seconds) since authentication. If the last time the user authenticated is greater than this value, the user must be reauthenticated.
Optional organizationThe organization to log in to.
This will specify an organization parameter in your user's login request.
org_), it will be validated against the org_id claim of your user's ID Token. The validation is case-sensitive.org_), it will be validated against the org_name claim of your user's ID Token. The validation is case-insensitive.
To use an Organization Name you must have "Allow Organization Names in Authentication API" switched on in your Auth0 settings dashboard.
More information is available on the Auth0 documentation portalOptional prompt'none': do not prompt user for login or consent on reauthentication'login': prompt user for reauthentication'consent': prompt user for consent before processing request'select_account': prompt user to select an accountOptional redirect_The default URL where Auth0 will redirect your browser to with the authentication result. It must be whitelisted in the "Allowed Callback URLs" field in your Auth0 Application's settings. If not provided here, it should be provided in the other methods that provide authentication.
Optional scopeThe default scope to be used on authentication requests.
This defaults to profile email if not set. If you are setting extra scopes and require
profile and email to be included then you must include them in the provided scope.
Note: The openid scope is always applied regardless of this setting.
Optional screen_Provides a hint to Auth0 as to what flow should be displayed. The default behavior is to show a login page but you can override this by passing 'signup' to show the signup page instead.
This only affects the New Universal Login Experience.
Optional segment_An optional segment identifier to pass alongside experiment_id and
variation_id when forcing a variant.
Optional session_Session transfer token from a native application for Native to Web SSO.
When sessionTransferTokenQueryParamName is set, this is automatically
extracted from the specified URL query parameter if present.
Optional ui_The space-separated list of language tags, ordered by preference.
For example: 'fr-CA fr en'.
Optional variation_The variation to force within the experiment identified by experiment_id.
Auth0 uses this value instead of computing an assignment for the current
request. The override applies to this request only; the next login without
these params reverts to normal server-side assignment.
If you need to send custom parameters to the Authorization Server, make sure to use the original parameter name.