To begin using the PingOne Platform APIs, you will need to complete the following tasks:
After you complete these tasks, you can make any PingOne API calls allowed by the permissions encoded in your access token. For general information about PingOne APIs, see Management APIs Overview and Authentication APIs Overview.
Application connections determine how PingOne integrates with client applications. When you define the application connection, you also define the application’s access to PingOne resources, which are encoded in the application’s access token. To make calls to the PingOne API, you must submit your access token with the API request.
To acquire an access token, you can use the Admin Console to configure your first application connection. To create the application connection:
The Applications page shows the new application. To view the application’s access token, you must enable the new application:
To get the access token:
To get your environment ID from the Admin Console:
The Properties page shows the environment ID.
Your PingOne account has at least one defined environment resource. You can use the PingOne APIs to return information about the environment resource associated with your application connection.
In the North America (NA) region:
curl -X GET "https://api.pingone.com/v1/environments/{environmentId}" \
-H "Authorization: Bearer jwtToken"
In the European Union (EU) region:
curl -X GET "https://api.pingone.eu/v1/environments/{environmentId}" \
-H "Authorization: Bearer jwtToken"
In the Asia Pacific (AP) region:
curl -X GET "https://api.pingone.asia/v1/environments/{environmentId}" \
-H "Authorization: Bearer jwtToken"
The jwtToken
value in your request is your full base64url-encoded access token generated by the PingOne authentication service. If your token is valid, the API request returns a 200: Successful operation
message. It also displays the property data for the environment and HAL links to show the related resources associated with the environment.