/users/{}/sessions* → endpoint removal
PagerDuty REST API
Deprecated, no date
PagerDuty deprecated /users/{}/sessions* endpoints without announcing a shutdown date. Subsequent calls will fail once removed. This change affects all requests targeting the deprecated sessions endpoint path.
Calls it hits
/users/{}/sessions*
What to use instead of these calls
List a user's OAuth delegations with GET /users/{id}/oauth_delegations instead. Revoke delegations using DELETE /oauth_delegations.
In PagerDuty REST API's words
This endpoint is deprecated, please use the [List OAuth Delegations endpoint](https://developer.pagerduty.com/api-reference/4f8e257df4468-list-a-user-s-delegations) instead.
Facts
- API
- PagerDuty REST API
api.pagerduty.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against PagerDuty REST API's own pages
Questions
When does this change take effect?
PagerDuty REST API deprecated /users/{}/sessions* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: PagerDuty REST 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.
More from PagerDuty REST API 1
-
No date
/incidents/custom_fields*Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.