Update: This guide can now be found in the API docs here: Postman Collections | SailPoint Developer Community
Here you will find the official Postman Workspace for IdentityNow APIs. If you have any questions, comments, suggestions, or issues with this workspace or any collections within, let us know here.
You will forever find the IdentityNow workspace here: IdentityNow Postman workspace
You can also click these buttons if you just want a single collection
When you navigate this link, you’ll see our workspace, and you’ll find the collections of APIs on the left-hand side. Read the following guide to learn how to use them:
- Hover over the collection you’d like to fork, click the ellipse on right-hand side, and click ‘Create a fork’.
- Choose a label for your forked collection, choose the workspace that you’d like to fork it into (usually “My Workspace,” unless you know what you’re doing), and ensure that ‘Watch original collection’ is checked.
- Click the ‘Fork Collection’ button.
To make things easier for you when using Postman, we’ve built our official workspaces around usage of Postman’s environments feature. With our latest update, we’ve added an environment to the postman workspace which you can fork in the same manner that you did the collection. This will allow you to get updates to the environment in the future as we continue to add new capabilities to our workspace. In case you decide to use your own, these fixes/improvements mean you’ll need to update your environments. You will need the following environment variables in your Postman environment:
|tenant||*||This is your IdentityNow tenant, typically your company’s name.|
|clientId||*||This is the client ID for the API client or personal access token.|
|clientSecret||*||This is the client secret for the API client or personal access token.|
|domain||This field is optional and is only needed for a select few who may have a domain in their API URL that differs from “identitynow”.|
This is the big one, right? What about when the APIs get updated? Thankfully, Postman has a feature built-in for this, and it ties back to your ensuring that the ‘Watch original collection’ option is checked.
All you have to do now to check for updates is this - in your own personal workspace where you forked the collection, do the following:
- Hover over the collection, click the ellipse on the right-hand side, and click ‘Pull changes.’
- If there are no new changes, then you are up to date. If there are new changes, it will look like the following image. Just click the Pull Changes button, and that’s it!
In addition to managing the collections for you, we’ll continue to add features as they’re requested and we can get to them. Got a collection/workspace level request? Let us know here!
To boot, we’ve added a collection feature to V3 APIs originally posted by @Rich_Miller on automating JWT creation and improved by @atarodia to automatically retrieve the token when it expires. Thanks to Richard and Animesh for their contributions!