GitHub Copilot Model Policy API: REST Endpoints Now Generally Available

GitHub has made REST endpoints for Copilot model policies generally available at four levels: enterprise, enterprise team, enterprise app and organization. The change, posted to the GitHub changelog on October 19, 2026, lets administrators read and change which models Copilot can use without going through the settings interface.

The endpoints are GET and PATCH pairs. The four paths are:

• /enterprises/{enterprise}/copilot/model-policies
• /enterprises/{enterprise}/teams/{team_slug}/copilot/model-policies
• /enterprises/{enterprise}/copilot/apps/model-policies
• /orgs/{org}/copilot/model-policies

According to GitHub, the endpoints are meant to make it easier to manage Copilot model availability across an enterprise. The company says enterprise policies can delegate model control to organizations in organization mode, or to teams and apps in enterprise teams mode.

For teams running Copilot across many organizations, the API route is likely the practical one. Instead of changing model settings by hand in each place, an admin can script the reads and updates and keep the same policy applied everywhere. The PATCH side is what actually changes a policy; the GET side is for checking what is currently set.

GitHub points users to its documentation on managing the availability of models in an enterprise, and to its REST API documentation, to get started. The changelog does not list pricing, rate limits or a deprecation date for any older method of managing model policies.

If you administer Copilot for an enterprise or an organization, the endpoints are live now, so you can call them against your existing enterprise or organization slug. Check your current policies with GET before you PATCH anything, and review the enterprise model availability documentation first if you plan to hand control down to organizations, teams or apps.

Related reading

Sources

• Copilot model policy API for enterprise, orgs, and teams — GitHub Changelog