Listing Identities

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Greetings,

Just getting going with the ISC APIS, and running into an issue listing all of the Identities in our dev Tenant:

Given the following request ( Derived from Postman Request )

curl --location ‘https://[TENANT PORTION].api.identitynow-demo.com/v2025/identities?limit=250&offset=0’ \

--header ‘Accept: application/json’ \

--header ‘Authorization: ••••••’

Receiving the following response:

`"detailCode": "403 Forbidden",`

"trackingId": "0a3fe85b98ce4bff8eeb73397d502fb9",
"messages": [
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The server understood the request but refuses to authorize it."
},
{
"locale": "und",
"localeOrigin": "REQUEST",
"text": "The server understood the request but refuses to authorize it."
}
],
"causes": []

In terms of our general setup, I am have an API Client with the following scopes defined:

idn:identity:read,sp:scopes:all,idn:identity:manage

We are able to pull retrieve Accounts, using the Accounts List endpoint, as well as getting detailed information, using the Account Details endpoint.

Looking for a little guidance on the proper request, or anything that we may be missing here.

2

Hello @dspencer_anaqua, Could you maybe check if Your case is related to this? API read scopes - 403 forbidden error - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community

3

Switch to a Personal Access Token (PAT) instead:

  1. Go to your profile → Preferences → Personal Access Tokens

  2. Create a new PAT with the same scopes (idn:identity:read, idn:identity:manage, or just sp:scopes:all)

  3. Make sure the user creating the PAT has ORG_ADMIN or appropriate user level permissions

  4. Use the PAT’s client ID/secret to authenticate—it works exactly like client credentials but carries the user context

The difference:

Client credentials = no user context.
PAT = tied to the user who created it.

Many ISC APIs require that user context for authorization, which is why Accounts endpoints work but Identities doesn’t.

Hope this helps.

4

@sita_ram Thank you for the clarification. I, had created the PAT previously, but must have gotten lost in the shuffle was I was coming up to speed on the platform. All is good now!

5

Great! Please mark this as the solution so it can help other developers. Thanks.