PingOne Platform APIs

Using the PingOne Postman environment

The PingOne use case collections include test scripts that write environment variables and their current values to your active Postman environment for the newly created PingOne resources.

To save and use these resource IDs, specify a Postman environment and have the following Postman environment variables set before you begin. Refer to The PingOne Postman Environment Template for the regional domains associated with the API endpoints for these environment variables:

  • {{tld}}

    The top level domain for your region:

    Region Code Top level domain

    North America region (excluding Canada)

    NA

    com (default)

    Canada region

    CA

    ca

    European Union region

    EU

    eu

    Australia region

    AU

    com.au

    Singapore region

    SG

    sg

    Asia-Pacific region

    AP

    asia

    This variable is incorporated in each of the following {{…​Path}} variables to make changing your region simple. When you set {{tld}}, the {{…​Path}} variables are also set to the appropriate region.

  • {{apiPath}}

    The regional domain for the PingOne server. These IDs identify a specific configured application in PingOne.

  • {{authPath}}

    The domain for the PingOne authentication server.

  • {{orchestratePath}}

    The regional domain (and part of the path) for the PingOne DaVinci server.

  • {{scimPath}}

    The regional domain (and part of the path) for the PingOne SCIM server.

  • {{envID}}

    The UUID of an environment resource. This ID identifies your current working domain within your organization.

  • {{accessToken}}

    A valid access token returned by the PingOne authorization server from the worker application in your current environment. For information about creating a worker application and getting an access token, refer to Create an admin Worker app connection.