GitHub REST API
GET /users/{id}/subscriptions endpoint removal
Deprecated, no dateSubscribe to GitHub REST APIShare
GitHub deprecated GET /users/{id}/subscriptions without a shutdown date. During the deprecation period, the endpoint stays accessible but returns empty responses. Calls will eventually fail when full removal occurs in a subsequent phase.
Calls it hits
GET /users/{id}/subscriptions
What to use instead of these calls
No replacement is offered because the list of repositories a user watches is no longer exposed.
In GitHub REST API's words
During the deprecation period, the endpoint will remain accessible but will return empty responses. Full removal will occur in a subsequent phase.
Facts
- API
- GitHub REST API
api.github.com - Kind
- Endpoint removal
- Announced
- June 30, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against GitHub REST API's own pages
Questions
When does this change take effect?
GitHub REST API deprecated GET /users/{id}/subscriptions without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: GitHub 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 GitHub REST API 10
-
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
GET /assignments/*Endpoint removal Stopped working -
GET /classrooms*Endpoint removal Stopped working -
GET /repos/{id}/{id}/dependency-graph/sbomEndpoint removal Stops workingin 7 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.