Create Team
Creates a new developer team. Teams can be organized around developers (by adding members), repositories (by assigning repos), or both. You can also create empty teams and add members/repos later via the update and member endpoints.
Use cases:
- Developer-based team: Pass
membersto group developers (e.g. a frontend squad). You can optionally passrepositoriesas a filter to scope metrics to specific repos for this team. - Repository-based team: Pass only
repositoriesto group repos (e.g. all microservices). No members — metrics are aggregated across the listed repos. - Mixed team: Pass both
membersandrepositories— metrics are scoped to these members across these repos. - Disabled lists: Create special teams named
codeant-disabled-membersorcodeant-disabled-reposto exclude specific developers or repositories from all metrics calculations across the organization.
Optionally assign one or more team_leads (by login) and categorize teams with tags. Teams can be nested using parent_team_id.
Documentation Index
Fetch the complete documentation index at: https://docs.codeant.ai/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Access token for the git provider (GitHub PAT, GitLab PAT, Bitbucket App Password, Azure DevOps PAT). Pass via Authorization: Bearer <token> header.
Body
Version control platform
github, gitlab, bitbucket, azure_devops, azuredevops "github"
Organization, workspace, or group name on the platform
"my-org"
Team name (min 2 characters)
2"Backend Team"
Base URL for GitHub (use for GitHub Enterprise Server)
"https://github.com"
Base URL for GitLab (use for self-hosted GitLab instances)
"https://gitlab.com"
Base URL for Azure DevOps (use for Azure DevOps Server)
"https://dev.azure.com"
Base URL for Bitbucket (use for Bitbucket Data Center/Server)
"https://api.bitbucket.org/2.0"
Team description
"Responsible for API services"
Hex color code
"#1570EF"
["lead@example.com"]["my-org/backend-api"]Initial team members to add at creation. You can create a team with members, repositories, or both.
[
{
"user_login": "jane@example.com",
"user_name": "Jane Doe",
"role": "lead"
},
{
"user_login": "john@example.com",
"user_name": "John Smith",
"role": "member"
}
]Tags for categorizing the team
["backend", "api"]Parent team ID for creating nested/sub-teams
""
Identifier of who created the team
"admin@example.com"