API Patch Attribute - End Date

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

Hi Guys,

I need some help with the correct API Patch endpoint to use to update end date for identities. I am using the V3 endpoint as follows:

https://sailpoint.api.identitynow.com/v3/auth-users/:id (I would have updated the ID and tenant in postman). The image below shows the body details and the error message I’m getting.

Patch-Body
Patch-Body1966×1101 96.2 KB

I keep getting a bad request so I know that something is wrong with the details of the request, I’m just not sure how to do it even when I follow the documentation.
I am trying to test this in postman first to incorporate in a script I am working on but keep getting the error “The request could not be
parsed” and that its a bad request.

2

Hi @dcoleman , mentioned API doesn’t update identity attributes. It is to implement user authentication. You can check more about here Auth Users | SailPoint Developer Community.

In order to update any of identity attribute then you can use this API put-identity-attribute | SailPoint Developer Community

3

@JackSparrow ok, let me explore that API you mentioned and try again. Thanks for the prompt reponse.

4

@JackSparrow I tried the API and is getting a “Cannot
consume content type” error, however I’m not sure if that API can achieve exactly what I want. Just for clarity, I want to update the value of the attribute.

example: from
“attributeOldVal”:“2025-06-30” to “attributeNewVal”:“2025-07-07” ,

as oppose to updating the attribute itself. I wasn’t seeing anything on how to update the value of the attribute, hence why I was using a patch API before I just don’t think the endpoint was correct.

5

@dcoleman, the endDate identity attribute cannot be updated directly via the API. However, if this endDate is available in your authoritative source, it can be updated through that source.

Is this a one-time exception for updating endDate, or are you planning to do this on a regular basis?

If you need to implement a consistent and automated process, an alternative approach would be to use a delimited file source. You can include the endDate attribute in this source and map it to the endDate identity attribute in the identity profile.

This setup would allow you to update the attribute using:

  • API calls to the delimited source,
  • CSV file imports,
  • or a combination of forms and workflows.
6

Hi @baoussounda, yeah this will be often but I created an Attribute that maps to the endDate so I really want to update the attribute created but was using end date as an example, I wanted to test it with the correct API. Can the value of the attribute I created be updated VIA an API?

7

@dcoleman
You cannot directly update any identity attribute value via the API (except for the lifecycleState). However, as mentioned above, you can update the attribute value in the delimited source file, and any identity mapped to that value will be updated automatically