Okta API
POST /api/v1/org/privacy/oktaSupport/revoke endpoint removal
Stopped workingSubscribe to Okta APIShare
On January 15, 2025, the endpoint POST /api/v1/org/privacy/oktaSupport/revoke was fully deprecated. Calls targeting this endpoint now fail, as callers are no longer able to access it.
Calls it hits
POST /api/v1/org/privacy/oktaSupport/revoke
What to use instead of these calls
Use PATCH /api/v1/org/privacy/oktaSupport/cases/{caseNumber} (Update an Okta Support case) to revoke Okta Support access for each support case.
In Okta API's words
These endpoints will be fully deprecated on January 15, 2025. After deprecation, you won’t be able to access them.
Facts
- API
- Okta API
*.okta.com - Kind
- Endpoint removal
- Announced
- November 1, 2024
- Takes effect
- January 15, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Okta API's own pages
Questions
When does this change take effect?
Calls to POST /api/v1/org/privacy/oktaSupport/revoke stopped working on January 15, 2025.
What happens to calls after January 15, 2025?
They have failed since January 15, 2025.
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.
More from Okta API 2
-
POST /api/v1/org/privacy/oktaSupport/extendEndpoint removal Stopped working -
POST /api/v1/org/privacy/oktaSupport/grantEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.