PingOne Platform APIs

Downloading PingOne workflow collections

Workflow Retrieve

Add a Custom Claim to an Access Token

Run in Postman

Add a User through a Registration Flow

Run in Postman

Add User Image

Run in Postman

Assign a Role to a User

Run in Postman

Assign an MFA Sign-On Policy to a Web Application

Run in Postman

Audit for Agreement Consents

Run in Postman

Configure a DaVinci Non-redirect Flow

Run in Postman

Configure a Non-Interactive Worker Application

Run in Postman

Configure a Passwordless Sign-On Policy

Run in Postman

Configure a PingOne App to Use a DaVinci Flow Policy

Run in Postman

Configure a PKCE Authorization Workflow

Run in Postman

Configure a Progressive Profiling Sign-On Action

Run in Postman

Configure a SAML Identity Provider

Run in Postman

Configure a Simple Login

Run in Postman

Configure a Single-Page Application with an Implicit Grant

Run in Postman

Configure a Single-Page Application with PKCE and an AuthCode Grant

Run in Postman

Configure an Application to use the offline_access Scope

Run in Postman

Configure an Application with a Refresh Token Grant

Run in Postman

Configure an Application with an Authorization Code Grant

Run in Postman

Configure an External Identity Provider to Call a DaVinci Flow

Run in Postman

Configure an Interactive Worker Application

Run in Postman

Configure an MFA Sign-On Policy with an Authenticator App

Run in Postman

Configure an MFA-Only Flow Using a Login Hint Token

Run in Postman

Configure CLIENT_SECRET_JWT as the token auth method

Run in Postman

Configure Device Authorization Grant Flow

Run in Postman

Configure Facebook as an Identity Provider

Run in Postman

Create a Group and Add a User

Run in Postman

Create a Password Policy

Run in Postman

Create a Risk Evaluation

Run in Postman

Create a Risk Policy Set

Run in Postman

Create a Workday Propagation Connection

Run in Postman

Create an LDAP Gateway

Run in Postman

Create an MFA Transaction Approval using SMS

Run in Postman

Create and Assign App Roles

Run in Postman

Create and Update Notification Content

Run in Postman

Davinci Flow Execution Detailed Responses

Run in Postman

DaVinci Flow Execution Registration

Run in Postman

DaVinci Flow Execution Sign-on

Run in Postman

Download an Integration Binary

Run in Postman

Exchange a Refresh Token

Run in Postman

Find and Terminate a User Session

Run in Postman

Get a Token for Custom Resource Access

Run in Postman

Get an ID Token

Run in Postman

SAML Sign-On

Run in Postman

Show PingOne Authorize App Permissions in Token

Run in Postman

Sign-Off User Session

Run in Postman

Sign-on using an External Identity Provider

Run in Postman

Test a SAML Application Connection

Run in Postman

Test an OAuth Connection using Identifier First Authentication

Run in Postman

Test an OIDC Application Connection

Run in Postman

Use an authentication JWT for token fulfillment

Run in Postman

Use an Email MFA Action to Authenticate Users

Run in Postman

Use LOGIN and AGREEMENT Actions to Authenticate Users

Run in Postman

Use LOGIN and MFA Actions to Authenticate Users

Run in Postman

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: com, ca, eu, com.au, sg, or 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.