Initiates a request for authorization of a Connected App
scope, client_id, redirect_uri, prompt, etc…) are correct and returns relevant information for rendering an OAuth Consent Screen.
This endpoint returns:
user_idsession_tokensession_jwtsession_token or session_jwt is passed, the OAuth Authorization will be linked to the user’s session for tracking purposes. One of these fields must be used if the Connected App intends to complete the Exchange Access Token flow.Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Request type
The ID of the Connected App client.
The callback URI used to redirect the user after authentication. This is the same URI provided at the start of the OAuth flow. This field is required when using the authorization_code grant.
The OAuth 2.0 response type. For authorization code flows this value is code.
An array of scopes requested by the client.
The unique ID of a specific User. You may use an external_id here if one is set for the user.
The session_token associated with a User's existing Session.
The session_jwt associated with a User's existing Session.
Space separated list that specifies how the Authorization Server should prompt the user for reauthentication and consent. Only consent is supported today.
Successful response
Globally unique UUID that is returned with every API call. This value is important to log for debugging purposes; we may ask for this value to help identify a specific API call when helping you debug an issue.
The unique ID of the affected User.
The user object affected by this API call. See the Get user endpoint for complete response field details.
Whether the user must provide explicit consent for the authorization request.
Details about each requested scope.