Thank you for reporting this. I have opened an engineering ticket (ISCAIM-24250) to fix it. In the meantime, you will have to use sp:scopes:all to use this endpoint, which is understandably not the greatest option.
I am very sorry to hear that you’re not checking for similar issues as well, as there are many differences, and I find that comparing the two lists is not that complicated.
Would it not be more time efficient (for SailPoint and for us) to fix it completely instead of waiting for the next bug report with the next scope?
I agree that the suggestion made by @adamian would be the best, to have a single resource go through all the different end points to see if the mentioned scope actually exists. It may be a tedious job, but it looks like this is what needs to be done if the QC isn’t properly done when creating / generating the docs & end points.
It took me about 10 minutes to download the documentation from GitHub, grep it for scopes and compare it with the list of scopes from the UI. Let’s not overestimate the effort of having a good product.