{"id":94409,"date":"2026-03-12T09:00:07","date_gmt":"2026-03-12T16:00:07","guid":{"rendered":"https:\/\/github.blog\/changelog\/2026-03-10-rest-api-version-2026-03-10-is-now-available"},"modified":"2026-03-12T09:15:30","modified_gmt":"2026-03-12T16:15:30","slug":"rest-api-version-2026-03-10-is-now-available","status":"publish","type":[3521],"link":"https:\/\/github.blog\/changelog\/2026-03-12-rest-api-version-2026-03-10-is-now-available","title":{"rendered":"REST API version 2026-03-10 is now available"},"content":{"rendered":"\n
Previously, we introduced calendar-based versioning<\/a> for our REST API, giving us a path to evolving our API while giving integrators plenty of time and clear guidance for upgrading.<\/p>\n Now, we’re releasing calendar version Version As a reminder, non-breaking changes (e.g., new endpoints, optional parameters, additional response fields) continue to be available across all supported API versions.<\/p>\n Version When you’re ready to upgrade, it’s straightforward. After reviewing the new version documentation and making any necessary changes to your integration to account for breaking changes, update the Use the version picker in our API documentation<\/a> to view the docs for all available versions.<\/p>\n We’ll continue to communicate future API version releases through the GitHub changelog. <\/p>\n We’d love for integrators to adopt Previously, we introduced calendar-based versioning for our REST API, giving us a path to evolving our API while giving integrators plenty of time and clear guidance for upgrading. Now, we’re…<\/p>\n","protected":false},"author":2106,"featured_media":0,"template":"","meta":{"_gh_post_show_toc":"","_gh_post_is_no_robots":"","_gh_post_is_featured":"","_gh_post_is_excluded":"","_gh_post_is_unlisted":"","_gh_post_related_link_1":"","_gh_post_related_link_2":"","_gh_post_related_link_3":"","_gh_post_sq_img":"","_gh_post_sq_img_id":"","_gh_post_cta_title":"","_gh_post_cta_text":"","_gh_post_cta_link":"","_gh_post_cta_button":"","_gh_post_recirc_hide":"","_gh_post_recirc_col_1":"","_gh_post_recirc_col_2":"","_gh_post_recirc_col_3":"","_gh_post_recirc_col_4":"","_featured_video":"","_gh_post_additional_query_params":"","footnotes":"","primary_cta":"","primary_cta_url":"","secondary_cta":"","secondary_cta_url":""},"label":[1751],"group":[3810],"coauthors":[3100],"class_list":["post-94409","changelog","type-changelog","status-publish","hentry","changelog-type-new-releases","changelog-label-ecosystem-and-accessibility","changelog-group-03-2026"],"yoast_head":"\n2026-03-10<\/code><\/strong>, the newest version of the GitHub REST API. This is the first calendar version to include breaking changes<\/strong>.<\/p>\nWhat’s in this release<\/span><\/a><\/h2>\n
2026-03-10<\/code> introduces a set of breaking changes to the REST API. You can find the full list of changes, along with upgrade guidance<\/a>, in our breaking changes documentation<\/a>. <\/p>\nWhat this means for existing integrations<\/span><\/a><\/h2>\n
2022-11-28<\/code> will continue to be fully supported for at least 24 months from today, and requests that don’t include the X-GitHub-Api-Version<\/code> header will continue to default to 2022-11-28<\/code>.<\/p>\nX-GitHub-Api-Version<\/code> header to 2026-03-10<\/code> and verify that your integration works as expected with the new API version.<\/p>\nWhat’s next<\/span><\/a><\/h2>\n
2026-03-10<\/code> to take advantage of the latest enhancements and features. While there’s no pressure to upgrade immediately, moving to the new version will help ensure your integration remains compatible and benefits from ongoing improvements as we continue to release new versions over time.<\/p>\n<\/body><\/html>\n","protected":false},"excerpt":{"rendered":"