Bulk Update Access Request Approval config API not working as expected

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

Hi All,

I am trying to update approvals config on bulk, basically the timeout option of approvals , on default the value is 90 days, but as per my project requirement it needs to be 7 days I am using the following api , it is showing 200 ok response when i submit the request, howeever when i fetch individual approval and see the config that timeout option is still showing as 90 days.
Any help on this would be highly appreciated. Thanks in advance!

API:{{baseUrl}}/v2025/generic-approvals/config/ACCESS_REQUEST_APPROVAL/APPROVAL_TYPE
Body:{

"timeoutConfig": {

    "enabled": **true**,

    "daysUntilTimeout": 8,

    "timeoutResult": "EXPIRED"

}

}

2

Hi @Shireesha5

I think the issue may be with the update flow, not necessarily the timeoutConfig values themselves.

For this API(HTTP-Verb), the safest pattern is usually:

  1. GET the current config first
  2. Update the part you need
  3. PUT the full config back
  4. GET again to verify the change actually persisted

For example:

GET /v2025/generic-approvals/config/ACCESS_REQUEST_APPROVAL

Then update it with something like:

PUT /v2025/generic-approvals/config
Content-Type: application/json

{
  "id": "ACCESS_REQUEST_APPROVAL",
  "timeoutConfig": {
    "enabled": true,
    "daysUntilTimeout": 7,
    "timeoutResult": "EXPIRED"
  }
}

A couple things I’d check:

  • Make sure you’re updating the correct endpoint
  • Make sure the body includes the expected config identifier
  • After the PUT, run the GET again and confirm whether the value really changed or if it still shows 90

If the PUT succeeds but the follow-up GET still returns the old value, then it’s probably not a payload issue anymore. It’s more likely platform-side behavior or a backend/UI mismatch.

So I’d troubleshoot it as:

GET → modify → PUT → GET again

That usually tells you pretty quickly whether the config is actually being saved or not.

3

Hi @Shireesha5 ,

Your updated config is only applied for new access request and not already existing approval items.

Have you tried or can you try to submit a new access request and check if the timeout is updated on this new approval item ?

4

Hi @Ousmane NDIAYE

Thank you for looking into the issue.

Yes you are correct, that change is applicable only for newly created request after this update and not applicable for the requests those created earlier this change.
With this explanation my issue got resolved. Thanks again!

1 Like
5

Hi @iamkiran

Thank you for checking the issue! Appreciate your help.

6

@Shireesha5
No Problem. Happy to help