Team Collaboration
APIGit brings your whole API team into one Git-native workspace. Organizations group the repositories of a product line or a partner program, teams carry the permissions, and every change to a spec, a document or a mock server arrives as a pull request that colleagues review before it ships. Nothing is bolted on: it is the Git workflow your developers already know, applied to APIs.
Organizations and Teams as Your Shared Workspace
Create an organization for each product line, platform or partner program and keep its API repositories together. Teams decide who gets in: give a team access to every repository of the organization or only to the ones you assign, and let the right people create new repositories.
- Organizations with their own repositories, members, teams and governance rules
- Teams scoped to all organization repositories or to an assigned set
Fine-grained Permissions for Every Team
Each team carries its own permission table: no access, read or write for the repository code, the issues, the pull requests, the published API documents and the mock servers. Reviewers read and comment, designers push to branches and open pull requests, and administrator teams manage settings, publishes and access, with the owner team in control of the whole organization.
- No access, read or write per unit: code, issues, pull requests, documents and mock servers
- Administrator access and the owner team for the people who run the organization
Review Every API Change in a Pull Request
Work on a branch, open a pull request and let the team review the diff of the spec, the documents and the mock scripts side by side. Governance checks run on the changed files, reviewers comment and approve, and the merge is the moment the change becomes the team's truth.
- Branch-based workflows with reviewers, labels and discussion
- Governance results on the changed files before the merge decision
Benefits of Collaborating in APIGit
Everything an API team needs to work together lives next to the specs themselves
Organizations
A shared home for the repositories, members and governance rules of each product or program.
Teams
Group colleagues by role and scope each team to all repositories or to the ones you assign.
Role-based permissions
Read or write per unit, from code and pull requests to published documents and mock servers.
Pull request reviews
Every change to a spec, a document or a mock is reviewed on a branch before it is merged.
Issues and labels
Track design questions, bugs and tasks next to the API they concern, with labels and assignees.
Seats and single sign-on
Add colleagues to your seats as the team grows, and sign them in through your identity provider on the Enterprise plan.
Ready to bring your API team together?
Start with an organization, invite your colleagues and review your first API change as a team, all in one Git-native workspace.