GitHub to restrict access to public API endpoints and UI views
GitHub is restricting access to several public API endpoints and UI views, including the stargazers, watchers, and user subscriptions endpoints. This change aims to prevent misuse of public data for spam and enhance platform security. Admins and collaborators will retain access, while some users may encounter empty responses or 403 errors.
- →Deprecate user subscriptions API endpoint
- →Restrict access to stargazers and watchers API endpoints
- →Restrict access to stargazers UI views
- →Rationale for access restrictions
Breaking changes (2) ›
- Restrict access to stargazers and watchers API endpoints
Access to the /repos/{owner}/{repo}/stargazers and /repos/{owner}/{repo}/subscribers API endpoints will be limited to admins and collaborators. Users may see empty responses or 403 errors.
- Restrict access to stargazers UI views
The Repository stargazers view and the Repository 'You Know' stargazers view will have their access restricted. Users may experience empty responses or 403 errors when accessing these views.
Deprecations (1) ›
- Deprecate user subscriptions API endpoint
The /users/{username}/subscriptions endpoint will be deprecated and its underlying information removed. During the deprecation period, it will return empty responses before full removal in a later phase.
Notes (1) ›
- Rationale for access restrictions
These changes are being implemented to protect users, prevent misuse of public data for spam activities, and strengthen platform security. GitHub will continue monitoring usage and evaluating further safeguards.
https://github.blog/changelog/2026-06-30-upcoming-access-restrictions-to-public-api-endpoints-and-ui-views