🎉 Postman: Incoming Fixes and Improvements! 🎉

:bangbang:We sincerely apologize to those of you who may have received 100+ emails from Postman about the updates to the workspace/collection. Unfortunately this was out of our control and a “feature” of the Postman platform. We will reach out to Postman about a solution to this for future updates.

We love all the feedback we’ve received over the last 5 months on how you’ve all been using our official Postman workspace and the different ways you’ve made changes or improvements. Today, we’ve made some improvements to the IdentityNow workspace that require your attention! We will retroactively update the Postman guide on this, but we’ll let you know here as well.

As always, let us know your thoughts here!


  • Pre-request script now works in the browser
  • Pre-request script no longer fails the first time a request is ran
  • Endpoint versions were moved from from a collection variable to each endpoint
  • You can now fully utilize Postman environments for each IdentityNow environment you have (no more workarounds needed)
  • Added consistency to variable naming conventions
  • Added official environment to the IdentityNow Postman workspace

How to Update Your Postman Environment

You’ll notice that some of these changes were “breaking changes” to your Postman environment. Here’s what you need to do to get your Postman collection back in order:

Pull the Latest Changes

Right-click on your collection, and click Pull Changes to update your collection.

Update Your Postman Environment(s)

With this 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 keep your own, these fixes/improvements mean you’ll need to update your environments. You will need the following environment variables in your Postman environment:

:bangbang:Be sure you do not have baseUrl in your environment variables.

Environment Variable Required Description
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 great @jordan_violet!
I had a question on the way the APIs will update when we hit “Pull Changes” on the Postman collection. If my APIs have been saved with some data like the JSON body, some query parameters etc., do they have to be reconfigured again after the update, or will the changes not affect that?

Also wanted to understand what happens to an existing JSON body when, say, the newer versions make changes to the JSON body syntax/structure. I’m guessing that would need some manual changing, but I could be wrong.

Hey Sushant,

That’s a really great question. I’m going to see if I can find a way to test this with Postman today, because I’m not actually sure what would happen there. In the meantime, what I can tell you is that we did not make any changes to any request bodies or query parameters. We only made changes to:

  • collection-level auth
  • collection-level variables
  • collection pre-request script
  • URLs for each endpoint

Got it, thanks Jordan.
I’m sure this is really going to save a ton of time and simplify testing on multiple tenants! :tada:

1 Like

Absolutely! Let us know what you think :slight_smile:

Promising start, but hit a question pretty quick. New variable on the Beta {{accessToken}} is not defined anywhere from what I can tell. Where/How is the {{accesstoken}} supposed to be defined and populated? Thanks!

That will be created by the pre-reqeust script the first time you run a call. Give it a run and let me know what happens.

Hello @sushant1,

I just tested this out and the “Pull Changes” will not overwrite any post JSON bodies or query parameters.

If there are any conflicting parameters, for example if we updated the offset parameter to 5 from 0 on one of the GET calls. Postman would recognize the difference and ask you if you would like to merge in the new changes.

Let us know if you have any other issues!


Thanks @tyler_mairose @jordan_violet!

I’m also working on a collection runner on Postman that we can use to semi-automate deployments with IdentityNow APIs. For now, the API calls have to be made manually (unless an external app is built which leverages the APIs) and that can sometimes be time consuming during large deployments/migrations.

I have a thread added here, and will keep you posted if I could make any progress on that front! But please let me know if you have any ideas, as this has potential to reduce a ton of unintended human errors.

I can’t figure out how to authenticate now that I’m using your latest greatest in Postman. Previously, in Postman, I would open the top level (IdentityNow Beta APIs) and use options on the page that opened to “Get New Access Token”; the individual endpoints had “Inherit from parent”. And everything worked.

Now with the forked collection that specifies “Bearer Token”, I have the client/secret on the enviornment still, but on the collection there is not a “Get New Access Token” button. When I run the “List Latest Invocation Statuses” endpoint, I get the error

    "error": "invalid_token",
    "error_description": "Cannot convert access token to JSON"

Unfortunately with Event Triggers, logs are only available for 24 hours so I only have until ~9pm EST to get the logs or we will have to complete another load test. So even though this is “Developer Days” I sincerely hope someone has time to point me to guidance. Thanks!

Hello Jordan,
Can I get the link to the most recent postman collection? I am unable to generate an access token despite setting up the environment credentials witht the tenant name & client ID and client secret.

There was an error in evaluating the Pre-request Script:Error: Unexpected token u in JSON at position

Hey Zenia,

Someone from my team will reach out to you in a direct message to help :slight_smile:

Hi @jordan_violet ,

I have created a global variable with tenant, clientID and Secrete but still gets same error:

I am getting below error in Postman console:

~ POST https://undefined.api.identitynow.com/oauth/token

Error: getaddrinfo ENOTFOUND undefined. api.identitynow.com

~ Request Headers

User-Agent: "PostmanRuntime/7.32.3'

Accept: "*/*"

Postman-Token: "5404099d-b300-4189-a6d0-d8e84b0819c8'

Host: "undefined.api.identitynow.com

Accept-Encoding: "gzip, deflate, br"

Connection: "keep-alive"

• Request Body

why am i getting host as undefined.api.sailpoint.com?

Hey @dheerajk27,

This would indicate that the tenant variable is not being parsed correctly.

Can you share how exactly you configured that variable?

Hi @LukeHagar ,

Thankys for the response, below is my Global environment entry:

And below is the postman call:

Hi @LukeHagar,

Looks like issue was with my environment which is fixed now.

Good morning. I’m getting deeper into APIs, and I’m setting up my workspace. I’m getting the following error when running GET List Transforms:

There was an error in evaluating the Pre-request Script:Error: Unexpected token u in JSON at position 0