{"meta":{"title":"Breaking changes","intro":"Learn about breaking changes that were introduced in each REST API version.","product":"REST API","breadcrumbs":[{"href":"/en/enterprise-server@3.20/rest","title":"REST API"},{"href":"/en/enterprise-server@3.20/rest/about-the-rest-api","title":"About the REST API"},{"href":"/en/enterprise-server@3.20/rest/about-the-rest-api/breaking-changes","title":"Breaking changes"}],"documentType":"article"},"body":"# Breaking changes\n\nLearn about breaking changes that were introduced in each REST API version.\n\n## About breaking changes in the REST API\n\nThe GitHub REST API is versioned. The API version name is based on the date when the API version was released. For example, the API version `2026-03-10` was released on Tue, 10 Mar 2026.\n\nBreaking changes are changes that can potentially break an integration. Breaking changes will be released in a new API version. We will provide advance notice before releasing breaking changes. Breaking changes include:\n\n* Removing an entire operation\n* Removing or renaming a parameter\n* Removing or renaming a response field\n* Adding a new required parameter\n* Making a previously optional parameter required\n* Changing the type of a parameter or response field\n* Removing enum values\n* Adding a new validation rule to an existing parameter\n* Changing authentication or authorization requirements\n\nAny additive (non-breaking) changes will be available in all supported API versions. Additive changes are changes that should not break an integration. Additive changes include:\n\n* Adding an operation\n* Adding an optional parameter\n* Adding an optional request header\n* Adding a response field\n* Adding a response header\n* Adding enum values\n\nWhen a new REST API version is released, the previous API version will be supported for at least 24 more months following the release of the new API version.\n\nFor more information about API versions, see [API Versions](/en/enterprise-server@3.20/rest/about-the-rest-api/api-versions).\n\n## Upgrading to a new API version\n\nBefore upgrading to a new REST API version, you should read the section on this page that corresponds to the new API version to understand what breaking changes are included and to learn more about how to upgrade to that API version.\n\nWhen you update your integration to specify the new API version in the `X-GitHub-Api-Version` header, you'll also need to make any changes required for your integration to work with the new API version.\n\nOnce your integration is updated, test your integration to verify that it works with the new API version.\n\n<!-- markdownlint-disable liquid-quoted-conditional-arg search-replace GHD046 -->"}