@justinrhaines, great catch! It’s actually blank by design, and I’ll need to fix the ones that say sailpoint to be blank. All you’ll need to do fill in that variable at the collection level and you’re set for all requests. This is by design from Postman.
I’ve fixed the Beta collection that had sailpoint as the variable.
Relative novice question: where is “api-url” supposed to be defined? I’m trying to run “List Latest Invocation Statuses” on the Beta API. It returns ‘Pre-request Script:Error: “undefined” is not valid JSON’ which the Postman console shows “POST http://undefined/oauth/token”. ‘api-url’ is in line 1 of the Pre-request Script, but not defined anywhere. I got passed this yesterday, but similar changes today didn’t work. I’ve added tenant to the Environment, but doing the same with the api-url just delayed the error (and frankly, I got it to work yesterday without doing that). Sorry if I’ve missed where this documented and thanks for any help!
Hey @carla_richey,
You’ve not missed a beat! In fact, you’re so on top of it that we’ve made some changes today and are putting out an announcement within the hour.
Keep an eye out for that, read the changes/fixes carefully, and let me know if you’re able to get everything to work. IF not, we’ll get it sorted out for you! 
In case you missed it:
I am attempting to configure my postman environment and workspace and receiving the following jSon error: “Unexpected token u in JSON at position 0” when attempting to run Autentication:Get Tenant Information. Anyone else seen this?
@LukeHagar Just a suggestion, let me know what you think:
For variables used in the pre-request script, if you can add a fallback for clientId, clientSecret and tokenUrl similar to domain, You can eliminate the dependency on having environment variables configured for the collection to run:
Before:
After:
This isn’t the same error I was receiving. But…when I reported the error I was getting, the developer team were already working on a correction. As of this morning, I was able to use the Authentication endpoint so maybe they’ve resolved this error. If not, my best advice would be to check that your environment has all the required variables and that they have the correct values for your tenant.
I was able to obtain an access token, but when I made a GET request for ‘Lists all sources in IdentityNow,’ I encountered the issue where the response returned ‘JSONError: Unexpected token u in JSON at position 0.’ Has anyone else encountered and resolved this issue?
Yeah I am getting the same… reading thru things too. This was mentioned above as I dug thru:
What is this cc/private API collection? How do we use this? When I try to fork and use it it shows the error message. That error message looks like a pre-request script. Could you please guide how to use private collection and pre-request script to connect sailPoiint identitynow.
Have you correctly configured the environment variables such as clientId, clientSecret, tenant and domain? If not, please create the environment and enter the variables or fork the environment and enter the variables: Postman
CC/Private API collections are the set of APIs which will be deprecated in near future and they are subject to change. Do not use this APIs unless you can’t find anything in V3 or Beta.
We would need more specifics on the exact error message you’re getting, but I agree with @atarodia that it’s likely something in the environment variables. If you have the environment variables clientID, clientSecret, tenant, and domain configured properly this should work with all 4 of the SailPoint provided Postman collection so you could verify if these are correct using a V3 or BETA API call to confirm they’re setup correctly.
@tihara, I have received that error when the variables are not set correctly and I had “domain” unchecked. Check your collection settings.
@jordan_violet, are these collections or environments going to be updated for using both identitynow.com and identitynow-demo.com tenants? Or does someone have any suggestions on the best way to use both (other than forking twice and setting the variables accordingly)?
I’m using separate “Environments” defined in Postman to segregate my various client tenants (SBX/PRD - identitynow.com), partner tenants (identitynow-demo.com), and developer tenant (identitynow-demo.com)
All I do is select the environment from the dropdown in the upper right and run the API call which allows me to switch quickly between all the various tenants.
What Ed said is the correct solution
Just add “domain” to your environment and then set the value to identitynow-demo and you’ll be all set.
I just noticed the IdentityNow collection has numerous NERM collections all named the same and finding the latest is pretty hard without looking at the details of each collection and tracking the dates.
Hoping there’s something we can do going forward to make these easier to navigate.
