The new documentation does not contain a field to input the token when testing a request, making it impossible to test a request in the docs
2 Likes
@tyler_mairose Any update on the above? Happy to submit a support ticket if needed
Maybe I’m missing something, but doesn’t putting the version at the very end of a URI (e.g., https://sailpoint.api.identitynow.com`/roles/v1`) violate standard RESTful design principles? Why isn’t the base URL defined to include the version and endpoint target appended as is normally the standard?
1 Like
Hey @akkochman,
We’ve got a fix in for this. If you check it again it should be back to normal!
@tyler_mairose Is the new API version update not applicable for the devrel tenant?
communication about this indicated the old endpoints would be supported through 2028 but the changes seem to have broken the api support for Data Segmentation features, we do not use Access Request Segements but those may be impacted as well- is there a fix planned for this?
1 Like
Hey @emilyfgordon,
The old endpoints are still supported, if there has been a bug introduced for Data Segmentation the traditional support route with the details of the issue is the way to go for this. It will be triaged as normal and fixed appropriately.
question on that point- the old endpoints are still support as in- those versions of the api are still in production? OR those old endpoints are being routed to the matching endpoint in new version? IE is the old API supported or just the old API endpoint?
Hi Mitch, this was a conscious decision to put the version on the end to avoid confusion about the version applying to the entire collection and to avoid collisions with already existing v2 and v3 API endpoints. We did have a lot of discussion on this with architects internally and while not conventional, does not violate any design principles so it is perfectly acceptable to append the version to the end.
1 Like
The old endpoints are supported and are routing to their existing code through our API gateway and remain completely unchanged.
The new v1 endpoints are typically routing to the v2026 codebase, any new v2 or beyond endpoints will be net new code.
How does this affect the python SDKs? I’m having issues importing them all of the sudden and I’m not sure if it’s a versioning issue or what.
I just posted this: Python SDK Suddenly Failing to Import
1 Like