# List auth-user capabilities

**URL:** <https://developer.sailpoint.com/discuss/t/list-auth-user-capabilities/17583>\
**Category:** SHF Discussion and Questions\
**Tags:** identity-security-cloud, apis\
**Created:** [September 13, 2023, 7:24pm UTC](https://developer.sailpoint.com/discuss/t/list-auth-user-capabilities/17583 "2023-09-13T19:24:46Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sailor\_man38](https://avatars.discourse-cdn.com/v4/letter/s/d2c977/32.png) [@sailor\_man38](https://developer.sailpoint.com/discuss/u/sailor_man38)\
**Post date:** [September 13, 2023, 7:24pm UTC](https://developer.sailpoint.com/discuss/t/list-auth-user-capabilities/17583/1 "2023-09-13T19:24:46Z")

</div>

On the auth-user patch endpoint page, theres mention of using below endpoint to list the capabilities available, is this endpoint live yet? if i go to it, i get “unable to route request” error. the “ams” suggests to me its behind styxx or something

> **[patch-auth-user | SailPoint Developer Community](https://developer.sailpoint.com/idn/api/v3/patch-auth-user/#auth-user-update)**
>
> Auth User Update

> A list of valid capabilities can be found using the GET ams/v3/authorization/authorization-capabilities/ endpoint.

---

<div class="post-metadata">

**Author:** ![sailor\_man38](https://avatars.discourse-cdn.com/v4/letter/s/d2c977/32.png) [@sailor\_man38](https://developer.sailpoint.com/discuss/u/sailor_man38)\
**Post date:** [September 14, 2023, 12:46pm UTC](https://developer.sailpoint.com/discuss/t/list-auth-user-capabilities/17583/2 "2023-09-14T12:46:03Z")

</div>

update on this one, it seems to work via postman if i use a session token (grab access token for ui/session page) but i get the routing error if i use a PAT locally  
any thoughts on this?

---

<div class="post-metadata">

**Author:** ![gladstoneabrahamr](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gladstoneabrahamr/32/4232_2.png) [@gladstoneabrahamr](https://developer.sailpoint.com/discuss/u/gladstoneabrahamr)\
**Post date:** [September 21, 2023, 7:14pm UTC](https://developer.sailpoint.com/discuss/t/list-auth-user-capabilities/17583/3 "2023-09-21T19:14:47Z")

</div>

Hi @sailor_man38,

> Any route that doesn’t use `/cc` , `/beta` , or `/v3` are internal only routes. You won’t be able to call them yourself.

So those are expected to work only with the browser-based logins and not with the PAT tokens which are intended for Public REST Endpoints.

Reference for a similar question [here](https://developer.sailpoint.com/discuss/t/account-correlation-api-account-correlation-config/5986/3)

Hope this answers your question.

---

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [September 28, 2023, 1:33pm UTC](https://developer.sailpoint.com/discuss/t/list-auth-user-capabilities/17583/4 "2023-09-28T13:33:17Z")

</div>

Works for me with a PAT in Postman. What error are you getting specifically?

 ![image](https://global.discourse-cdn.com/sailpoint/original/2X/1/1c280907f51ce3eb2ef35852ab29a59a07def164.png)

---

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [October 20, 2023, 5:24pm UTC](https://developer.sailpoint.com/discuss/t/list-auth-user-capabilities/17583/5 "2023-10-20T17:24:54Z")

</div>

I see where the confusion is now. The description for [PATCH auth user](https://developer.sailpoint.com/idn/api/v3/patch-auth-user) mentions using an `ams` endpoint, but there exists a public v3 endpoint for getting the same information. The correct endpoint to use is [GET auth user details](https://developer.sailpoint.com/idn/api/v3/get-auth-user). I have opened a documentation ticket (DEVREL-1305) to fix that description.

---

<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 19, 2023, 5:25pm UTC](https://developer.sailpoint.com/discuss/t/list-auth-user-capabilities/17583/6 "2023-12-19T17:25:08Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [January 23, 2024, 6:21pm UTC](https://developer.sailpoint.com/discuss/t/list-auth-user-capabilities/17583/7 "2024-01-23T18:21:27Z")

</div>

The documentation for [PATCH auth user](https://developer.sailpoint.com/idn/api/v3/patch-auth-user) now explicitly states the available capabilities in the schema description. There is a ticket (PLTIN-6296) that will track the progress of a dedicated endpoint to list these capabilities in the future. In the meantime, please refer to the API spec for the available capabilities.
