Separate Entitlement Request Config API Rationale

The List Role and List Access Profile APIs include the accessRequestConfig directly in the core object response, and it can be updated with the corresponding PATCH APIs. However, entitlements require a separate API to both get and update the accessRequestConfig.

Can this be added to the core entitlement model and APIs? Update’s aren’t a significant issue, but writing a script to export the request configuration for entitlements requires querying every entitlement directly, which is excessive, slow, and inefficient.

1 Like

Hi @nsorlien ,
I believe try submitting a feature request to SailPoint via the developer community or through your CSM. May be highlight how this change would improve API efficiency, reduce complexity, and avoid excessive API usage, especially when dealing with large environments with many entitlements.