The Postman collection uses variables in the request URLs to specify UUIDs for PingOne resources within your organization. When you click the Run in Postman button here, the environment template downloads and installs automatically. With this environment template, you can associate your PingOne resource UUIDs with the common variables used in many of the requests.

For more information about using Postman environments, see the following topic in the Postman documentation: Environments in Postman.

In the PingOne Postman download collections, for POST requests that create a resource and return a resource ID, these requests include a script that automatically adds a resource variable to your active Postman environment template and uses the newly created ID as the value.

For example, the following request from the PingOne Postman collection creates a new user. This request URL contains variables for the API path and environment ID:

POST {{apiPath}}/environments/{{envID}}/users

To run this request, you must ensure the {{apiPath}} in the Postman environment template has the regional top level domain associated with your organization. See PingOne API domains for more information.

Almost every request in PingOne requires an environment ID. If you are working primarily in one environment for testing purposes, you should add your environment’s UUID to the active Postman template as the value for the {{envID}} variable. In addition, requests to PingOne Management API endpoints require a valid access token to authenticate the request. In the PingOne download collections, the token value is represented in the Postman environment template as the variable {{accessToken}}. For more information about getting a token, see Getting Started with the PingOne APIs.

With the {{tld}} and {{envID}} variables defined in your Postman template, and with a valid token value defined in the {{accessToken}} variable, you can run the request. If the request is successful, Postman adds a {{userID}} variable to the Postman template automatically, and it associates the new user’s id property value (the UUID of the new user) with this variable.

Variables you must value {#variables-you-must-value}

When you Download the PingOne Postman collections, your workspace receives a Postman environment variable template. Variables in the environment variable template that represent a resource in PingOne automatically receive a value when you create a new PingOne resource using Postman. A script on the Tests tab of each create request inserts the identifier of the resource it creates as the value of the variable associated with that resource. However, some variables essential to using Postman with PingOne are not valued automatically. You must manually add the correct value to the variables in this table before you make any requests in Postman.

Postman variable PingOne resource
adminAppID The Client ID of the worker app when you Create an application connection. Used with authorization type of Bearer Token.
adminAppSecret The Client Secret of the worker app when you Create an application connection. Used with authorization type of Bearer Token.
adminEnvID The identifier for your administrative environment. This should be the environment in which your worker app resides. This prevents accidentally overwriting your administrative environment identifier should you use the API in Postman to create a new environment, which will overwrite the existing envID.
envID The identifier for the environment in which you are running your Postman API requests.
orgID The identifier for your organization. In PingOne Console, click Environment and click Properties to view your organization identifier.
apiPath The regional domain for the PingOne management server. Options are: https://api.pingone.com/v1 for environments in the North America region (excluding Canada), https://api.pingone.ca/v1 for environments in the Canada region, https://api.pingone.eu/v1 for environments in the European Union region, and https://api.pingone.asia/v1 for environments in the Asia-Pacific region.
authPath The regional domain for the PingOne authorization and authentication server. Options are: https://auth.pingone.com for the North America region (excluding Canada), https://auth.pingone.ca for the Canada region, https://auth.pingone.eu for the European Union region, and https://auth.pingone.asia for the Asia-Pacific region.
orchestratePath The regional domain for the PingOne DaVinci management server. Options are: https://orchestrate-api.pingone.com/v1 for environments in the North America region (excluding Canada), https://orchestrate-api.pingone.eu/v1 for environments in the European Union region, https://orchestrate-api.pingone.ca/v1 for environments in the Canada region, and https://orchestrate-api.pingone.asia/v1 for environments in the Asia-Pacific region.
scimPath The regional domain for the PingOne DaVinci management server. Options are: https://scim-api.pingone.com/v1 for environments in the North America region (excluding Canada), https://scim-api.pingone.eu/v1 for environments in the European Union region, https://scim-api.pingone.ca/v1 for environments in the Canada region, and https://scim-api.pingone.asia/v1 for environments in the Asia-Pacific region.