New Organizations API
I pushed the new Organization API documentation today. You can now access and modify Organization and Team information for your repositories. The Org API managed to test the limits of…
I pushed the new Organization API documentation today. You can now access and modify Organization and Team information for your repositories.
The Org API managed to test the limits of the current GitHub API. Traditionally, the Repository API actions required only the name to update your repo information. This worked well since most of the repos that you modified were owned by your own user. With Organizations, this is no longer the case, so we deprecated several of the old Repository API actions. You are encouraged (but not required) to pass the user login and the repo name for these actions (check the docs for more details):
repos/delete/:repo
repos/set/private/:repo
repos/set/public/:repo
repos/keys/:repo
repos/key/:repo/add
repos/key/:repo/remove
repos/collaborators/:repo/add/:collaborator
repos/collaborators/:repo/remove/:collaborator
Thank you to all the developers that helped us out during the beta. We received some valuable feedback that helped us fine tune the APIs and ensure its consistency. If you are a developer that works with the API a lot, be sure to follow the API Support Forum for announcements on new API updates.
Written by
Related posts
Introducing Agent HQ: Any agent, any way you work
At Universe 2025, GitHub’s next evolution introduces a single, unified workflow for developers to be able to orchestrate any agent, any time, anywhere.
Octoverse: A new developer joins GitHub every second as AI leads TypeScript to #1
In this year’s Octoverse, we uncover how AI, agents, and typed languages are driving the biggest shifts in software development in more than a decade.
Announcing the 2025 GitHub Partner Award winners 🎉
GitHub celebrates its 2025 Partner Award winners, honoring global, regional, and technology partners for driving innovation, collaboration, and impact across the developer ecosystem.