Step 7: Send authorize request

GET {{authPath}}/{{envID}}/as/authorize?client_id={{dvFlowAppID}}&response_type=code&response_mode=pi.flow&login_hint_token={{hint}}&scope=openid profile

This example shows the GET /{{envID}}/as/authorize operation to send an authorization request to the PingOne authorization server.

Note: For authorization and flow requests, the PingOne endpoint domain is https://auth.pingone.com/ for North America.

In this request:

• {{envID}} represents your environment ID.

• response_type here has a value of code. In other cases, it can be token, id_token, or a combination of all three of these.

• client_id is the ID of the PingOne application that you created in a prior step.

• scope specifies the OpenID Connect (OIDC) user claims are included in the token.

• response_mode. Set this to pi.flow to allow the app to authenticate using the assigned flow policy without needing to handle HTTP redirections.

• login_hint_token. Setting this provides a way for the client to identify and authenticate the user. For information on creating a login_hint_token, see Create a loginhinttoken JWT.

:::info Note: In the Qodex collection, this request includes a Qodex pre-request script to create the login_hint_token property value before executing the request. :::

• The request returns a 200 message along with the JSON response from the DaVinci flow.

See the following topics to learn more:

• OpenID Connect/OAuth 2

• Authorization

• Authorize (authorization_code)

• Authorize (Browserless and MFA Only Flows)

Request Params