/v2025/access-requests returns a non-existent accessRequestId when revoking entitlements

Hello Community,

I am currently working with the API for revoking access requests. Whenever the JSON response returns with existingRequests, the accessRequestId that is returned is not the actual access request id used in the revoke operation, and doesn’t appear to exist anywhere within the tenant. Has anyone else experienced this, or found a solution?

Please provide the API details which you used and the sample response to dig more into it.