CircleCI is removing the branches field from the following v1 and v1.1 endpoints on December 7, 2026:
GET /api/v1/projectsGET /api/v1.1/projectsGET /api/v1/project/:vcs-type/:username/:repo/settingsGET /api/v1.1/project/:vcs-type/:username/:repo/settings
This change applies to CircleCI cloud. It doesn’t affect other v1 or v1.1 endpoints, API v2 or v3, or the trigger and rerun deprecation announced on October 7. If you don’t read the branches field from these responses, you don’t need to do anything.
To help you find any remaining use, we’ll run 24-hour brownouts from 00:00:01 to 23:59:59 UTC. During a brownout, these endpoints return responses without a value for the branches field. The schedule is below.
| Brownout #1 | Brownout #2 | Removal Date |
|---|---|---|
| November 17th, 2026 | December 1st, 2026 | December 7th, 2026 |
What you should do
- Use API v3 to get project and project settings information. Use
GET /api/v3/projects?filter[org_id]=<org-id>to list the projects in an organization. See also the API v3 announcement.
Test it now
Add ?shallow=true to the projects endpoints or ?skip-branches=true to the settings endpoints to see the new responses today.
Need more time?
Add ?shallow=false (projects) or ?skip-branches=false (settings) to keep the current behavior temporarily. These parameters will also be removed on December 7, 2026. If this timing is a problem for you, please let us know here or by contacting your CircleCI Technical Success Manager.