POST /orgs/{org}/teams
To create a team, the authenticated user must be a member or owner of {org}
. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see "Setting team creation permissions."
When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers
. For more information, see "About teams".
Servers
- https://api.github.com
Path parameters
Name | Type | Required | Description |
---|---|---|---|
org |
String | Yes |
The organization name. The name is not case sensitive. |
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
permission |
String | No |
Closing down notice. The permission that new repositories will be added to the team with when none is specified. Possible values:
Default value: "pull" |
notification_setting |
String | No |
The notification setting the team has chosen. The options are:
Possible values:
|
name |
String | Yes |
The name of the team. |
repo_names[] |
Array | No |
The full name (e.g., "organization-name/repository-name") of repositories to add the team to. |
description |
String | No |
The description of the team. |
parent_team_id |
Integer | No |
The ID of a team to set as the parent team. |
maintainers[] |
Array | No |
List GitHub IDs for organization members who will become team maintainers. |
privacy |
String | No |
The level of privacy this team should have. The options are:
Possible values:
|
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.