V2025 API: 400 Bad Request When Retrieving Access Requests (Works in v3)

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

I’m updating a PowerShell script to use the v2025 API instead of v3 for IdentityNow. The script retrieves access requests successfully using the v3 endpoint:

GET https://<tenant>.api.identitynow.com/v3/access-request-administration?limit=250&offset=0&count=true&request-state=EXECUTING

However, when I switch to the v2025 API (or try similar logic), I consistently get:

WARNING: Failed to retrieve access requests at offset 0
WARNING: The remote server returned an error: (400) Bad Request.

Details:

  • Authentication works (Bearer token).

  • Headers: Authorization: Bearer <token>, Accept: application/json.

  • Query parameters: limit, offset, count=true, request-state=EXECUTING.

  • Works fine with v3, fails with v2025.

Questions:

  1. What is the correct endpoint and query parameter format for retrieving access requests in v2025?

  2. Does v2025 still support pagination with limit and offset?

  3. Is request-state still valid, or has it changed in v2025?

Any documentation or examples for retrieving access requests via v2025 would be greatly appreciated!

Thank you!

2

Hey @KDelapaz !

You can find the documentation for the v2025 version of this endpoint here. My first thought is to make sure you are including the experimental header for this endpoint (X-SailPoint-Experimental=true).

Thank you,

  • Zach
2 Likes
3

Thank you, Zach! That was definitely the issue. I added the X-SailPoint-Experimental header, and everything is working perfectly now. I really appreciate your help!

4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.