Introducing SailPoint API v2026

Announcements Product News
6

Will these new v2026 APIs display consistent behavior?

For the v2025 APIs this is not the case. For example:

Take one of these object types: roles/workflows/custom user levels/access request approvals/work-items
Suppose I want to list all objects of those types, whose owner has id 1234abcd1234abcd1234abcd1234abcd. I would need to call the list API with the following url parameter:

parameter remark
filters=owner.id eq 1234abcd1234abcd1234abcd1234abcd Most API’s behave like this. I suggest this to be applied to the others
ownerId=“1234abcd1234abcd1234abcd1234abcd” Can’t add it in filters (perhaps combining it with AND/OR filtering) must use it direct as parameter, in camelCase
owner-id=“1234abcd1234abcd1234abcd1234abcd” Can’t add it in filters (perhaps combining it with AND/OR filtering) must use it direct as parameter, in kebab-case
filters=owner co Tom.Cole Can’t filter on id, only on name in contains mode. So this example also matches Tom.Coleman
unsupported Can’t filter on owner, even though this object type has an owner

(Here I have given the different behavior in random order. It can’t be immediately seen which object types I listed above they relate to. Ideally all these APIs display the same behavior, meaning we can filter on owner in the same way.)

Other examples of inconsistency exists as well:

  1. owner v.s. ownerRef v.s. ownerId
  2. Where the value owner.name comes from (uid v.s. displayname v.s. something else)
  3. How pagination works
  4. enabled: true v.s. disabled:false
  5. launchers have owners but they can’t be updated due to the API limitations. We have owners who left the organization who are still owner of these objects.

Since v2024, this new way of API versioning should make it easy to fix inconsistencies among the APIs. I have not seen the fixes in v2025. I hope the inconsistencies will be fixed in the v2026 APIs, and that new APIs are being tested to this consistent behavior, as I notice that new APIs are also not always consistent to what we would expect based on the already existing APIs.

Kind regards,
Angelo

A Discussion of SailPoint's API Versioning Strategy