Hi Jordan,
I am somewhat confused. From the article you posted (less than a year old):
SailPoint APIs that start with /v2 do not have the same urgency and will follow the 12-month EOL period from their individual deprecation announcement.
but
SailPoint now intends to turn off (sunset) ALL non-public API endpoints on March 31st, 2024.
So the first information about the 1 year EOL is not true in all/most cases (/v2 api), right?
We make sure to notify you when an endpoint reaches deprecation, so you have time to move over before it goes end of life.
I am not quite sure how this helps if the alternative is not ready yet. Take GET /api/app/list - #5 by colin_mckibben for example. This is going to be turned off at the end of March, but nobody can actually implement the alternative as there is no information about it. So it may be ready in 1 day, 1 month of 6 months. If it is more than 2 months, the “non-public” API will be turned off, right?
How it should work to make the customer lives easier:
Live/Production > Implement Alternative > Use it internally > Announce Deprecation > Wait 1 year > End of Life (eventually bundle multiple deprecations in one clear announcement)