Where to go from here
Now that you’ve successfully completed the workflows:
-
You’re all set up for the workflows in the Use Case Library, so you might want to go through any relevant use cases.
-
If you’re using Postman, or plan to, refer to The Postman Platform collection, and PingOne API domains for important information.
-
You’ll find more background on PingOne concepts and architecture in the topics in Foundations.
-
For similar workflows using the PingOne UI, refer to Getting Started with PingOne in the PingOne admin documentation.
| Refer to Forward compatibility guidance to ensure forward compatibility of your applications. |
Related information
For further information related to the workflows you just completed, refer to these topics:
The create a test environment workflow
Background information related to the create a test environment workflow:
The API requests you used in this workflow:
The PingOne Platform Postman collection
The Postman public collection for the PingOne Platform includes the requests for all create, read, update, and delete (CRUD) operations for the PingOne Platform APIs, the PingOne MFA APIs, the PingoOne Neo APIs, and the PingOne Protect APIs. The downloads also include a PingOne Postman environment template to help you assign values to variables in the request URLs.
| Description | Retrieve |
|---|---|
Postman requests for the PingOne platform API. Includes all environment variables. No example responses to make it easy to get started. |
|
Postman requests for the PingOne platform API. Includes all PingOne documentation and example responses. No environment variables are included. |
The PingOne Postman environment template
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, the environment variable template downloads and installs automatically. Using this environment template, you can associate your PingOne resource UUIDs with the common variables used in many of the requests.
POST requests that create a resource and return a resource ID, include a script in the Postman Script tab, that automatically adds a resource variable to your active Postman environment template and uses the newly created ID as the value.