GitHub REST API: API Changes (2026-01-16)

TL;DR

The /installation/repositories endpoint has undergone significant changes, affecting the response format and required properties.

Multiple properties have been removed from the response, including archive_url, archived, assignees_url, and others.

The changes are breaking, requiring immediate attention from developers.

The affected resources include /installation/repositories and /user/installations/{installation_id}/repositories.

Developers should review the updated API documentation to ensure compatibility with the new changes.

What Changed

#### Breaking

Changes that require immediate action:

The repositories/items/ response's property type/format changed from object/'' to ''/'' for status '200'.

Removed the required properties archive_url, archived, assignees_url, blobs_url, branches_url, clone_url, collaborators_url, comments_url, commits_url, compare_url, contents_url, contributors_url, created_at, default_branch, deployments_url, description, disabled, downloads_url, events_url, fork, forks, forks_count, forks_url, full_name, git_commits_url, git_refs_url, git_tags_url, git_url, has_downloads, has_issues, has_pages, has_projects, has_wiki, homepage, hooks_url, and html_url from the response with the '200' status.

Who's Impacted

If you are using the /installation/repositories endpoint, you will be impacted by these changes. If you are relying on the removed properties, you will need to update your code to accommodate the new response format. If you are using the affected resources, including /user/installations/{installation_id}/repositories, you should review the updated API documentation to ensure compatibility with the new changes.

Action Checklist

☐ Review the updated API documentation for the /installation/repositories endpoint.

☐ Update code to accommodate the new response format.

☐ Remove references to the removed properties, including archive_url, archived, assignees_url, and others.

☐ Test API requests to ensure compatibility with the new changes.

☐ Verify that error handling is in place for potential issues with the new response format.

☐ Review dependent systems and services that may be impacted by the changes.

☐ Update documentation and internal knowledge bases to reflect the changes.

☐ Communicate the changes to relevant stakeholders and team members.

☐ Develop a plan for rolling out the updates to production environments.

☐ Monitor API performance and error rates after implementing the changes.

☐ Perform thorough testing, including unit tests, integration tests, and end-to-end tests.

☐ Validate that the updates do not introduce any security vulnerabilities.

☐ Ensure that the changes are properly versioned and documented in the code repository.

☐ Review and update any affected CI/CD pipelines or automated workflows.

Verification

The information in this update brief is based on the following sources:

[Commit 794edf1272f9](https://github.com/github/rest-api-description/commit/794edf1272f90f338a05382b44026737b7160949)

[GitHub REST API Spec Diff](https://github.com/github/rest-api-description/compare/56668bf53ffc98e1d2478c441bac6bcc82f0ae83...794edf1272f90f338a05382b44026737b7160949)

Last verified at: 2026-02-17T13:04:36.984414+00:00