# Listing Identities

**URL:** <https://developer.sailpoint.com/discuss/t/listing-identities/184233>\
**Category:** SHF Discussion and Questions\
**Tags:** apis, identity-security-cloud\
**Created:** [October 1, 2025, 9:45pm UTC](https://developer.sailpoint.com/discuss/t/listing-identities/184233 "2025-10-01T21:45:40Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dspencer\_anaqua](https://avatars.discourse-cdn.com/v4/letter/d/b38774/32.png) [@dspencer\_anaqua](https://developer.sailpoint.com/discuss/u/dspencer_anaqua)\
**Post date:** [October 1, 2025, 9:45pm UTC](https://developer.sailpoint.com/discuss/t/listing-identities/184233/1 "2025-10-01T21:45:40Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![markomanium](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/markomanium/32/29738_2.png) [@markomanium](https://developer.sailpoint.com/discuss/u/markomanium)\
**Post date:** [October 1, 2025, 10:19pm UTC](https://developer.sailpoint.com/discuss/t/listing-identities/184233/2 "2025-10-01T22:19:30Z")

</div>

> [@dspencer\_anaqua](#):
>
> `"detailCode": "403 Forbidden"`

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](https://developer.sailpoint.com/discuss/t/api-read-scopes-403-forbidden-error/16866)

---

<div class="post-metadata">

**Author:** ![sita\_ram](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sita_ram/32/30498_2.png) [@sita\_ram](https://developer.sailpoint.com/discuss/u/sita_ram)\
**Post date:** [October 2, 2025, 4:37am UTC](https://developer.sailpoint.com/discuss/t/listing-identities/184233/3 "2025-10-02T04:37:19Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![dspencer\_anaqua](https://avatars.discourse-cdn.com/v4/letter/d/b38774/32.png) [@dspencer\_anaqua](https://developer.sailpoint.com/discuss/u/dspencer_anaqua)\
**Post date:** [October 2, 2025, 1:04pm UTC](https://developer.sailpoint.com/discuss/t/listing-identities/184233/4 "2025-10-02T13:04:34Z")

</div>

@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!

---

<div class="post-metadata">

**Author:** ![sita\_ram](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sita_ram/32/30498_2.png) [@sita\_ram](https://developer.sailpoint.com/discuss/u/sita_ram)\
**Post date:** [October 2, 2025, 1:49pm UTC](https://developer.sailpoint.com/discuss/t/listing-identities/184233/5 "2025-10-02T13:49:37Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [December 1, 2025, 1:50pm UTC](https://developer.sailpoint.com/discuss/t/listing-identities/184233/6 "2025-12-01T13:50:30Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.