POST /api/account/setAccountData

Replaced by

Hi @colin_mckibben we are attempting to replace /v2/accounts with /v3/accounts however we are having issues with the PATCH method.

When updating attributes via PUT it works fine:

PUT /v3/accounts/:id
{
    "attributes": {
        "Name": "abcabc",
        "Platform": "ABC",
        "Manager": "John"
    }
}
Response: OK

But via PATCH we get the below error:

Request:
PATCH /v3/accounts/:id
[
    {
        "op": "replace",
        "path": "/attributes/Platform",
        "value": "ABC"
    }
]
Response:
[/attributes/Platform is not a valid patch field for the account model.
]

Can confirm that Platform is a valid part of the account schema, and updating it via PUT works, but obviously it means we need to provide the entire account structure which given the workflow is much more challenging because we need to read the existing account, calculate the changes, etc.

Hi @Ramiro,

Currently, PATCH Operation will allow you to modify only two fields:

  • identityId
  • manuallyCorrelated

You can refer here: update-account | SailPoint Developer Community

Thanks for the feedback Ramiro. I will forward this on to the correct team. It certainly would be nice to patch individual attributes as opposed to having to do a full update.

I have to say, this API deprecation journey is frustrating to say the least. So far only about a third of the private APIs we use actually have replacements and of those only half of them are actually fit for purpose.

I don’t feel like much progress has been made in the 4 months since this was announced.

Are SailPoint actually going to provide us with the replacement APIs in time?