Accounts API version v2026 fails in multiple ways

Feedback Bugs
, ,
1

Hi all :slight_smile:

The v2026 API endpoints for accounts are failing.
Try getting a single account by passing the id in the URL.
Or by getting all accounts from a given sourceId. What worked in v2025 is no longer working in v2026, even though the API documentation is the same. Also the returned content type is wrong (application/octet-stream instead of application/json).

See: Accounts | SailPoint Developer Community

To make it work, you would need to go back to v2025.

Kind regards,
Angelo

2

@angelo_mekenkamp Hi Angelo, it’s working fine for me—could you share the exact error/details you’re seeing? I hope you are talking about this right {{baseUrl}}/accounts/:id

3

Hi @ROHPU, here are the screenshots. Can you share the screenshots where it is actually working from your end?

example failure get account by id (account id does exists):

image
image2440×544 84.7 KB

Same example with v2025 instead of v2026:
image
image2424×410 53.4 KB

example failure get all accounts (wrong content-type):

image
image2444×470 50 KB

Same example with v2025 instead of v2026:
image
image2448×458 50.8 KB

example failure get all accounts from specific source:

image
image2452×666 100 KB

Same example with v2025 instead of v2026:
image
image2444×446 63.9 KB

Kind regards,
Angelo

4

Sure

image
image1513×505 69.2 KB

7

Ahh yes @ROHPU, that shows that one of the three cases (get account by id API) works on your end. Perhaps you operate from a different region where the SailPoint API servers are configured properly? Have you tried the other two cases I mentioned as well? (content type when getting all accounts, and trying to get all accounts by filtering on sourceId?

8

@angelo_mekenkamp

I have tried same and it is failing for me also.

9

Thank you for confirming @sukarande. Do you experience the same issues @developer_advocates? If so, could you please follow up on this at SailPoint?

Kind regards,
Angelo

10

Hey @angelo_mekenkamp,

The accounts team is working on updates to their services, it appears those breaking changes were incorrectly added to v2026. It will only route to the new service if you have a feature flag enabled on your tenant. Your tenant must be one of the ones previewing the change with the feature flag enabled.

This is why one tenant might see the correct behavior while another is broken.

This will be sorted out in the coming weeks with the API versioning strategy updates, stay tuned!

2 Likes