Descope API
POST /v1/mgmt/tenant/adminlinks/sso/generate endpoint removal
Deprecated, no dateSubscribe to Descope APIShare
The endpoint POST /v1/mgmt/tenant/adminlinks/sso/generate is deprecated without a shutdown date. It generates tenant admin SSO configuration links using a valid management key. Once removed, requests to this endpoint fail.
Calls it hits
POST /v1/mgmt/tenant/adminlinks/sso/generate
What to use instead of these calls
Call POST /v2/mgmt/tenant/adminlinks/sso/generate instead.
In Descope API's words
Generate tenant admin SSO configuration link, using a valid management key. Deprecated: use the v2 endpoint at /v2/mgmt/tenant/adminlinks/sso/generate instead.
Facts
- API
- Descope API
api.descope.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Descope API's own pages
Questions
When does this change take effect?
Descope API deprecated POST /v1/mgmt/tenant/adminlinks/sso/generate without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Descope API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.