legacy_teams

Overview

Name	Datatype	Description
`id`	`integer`	Unique identifier of the team
`name`	`string`	Name of the team
`description`	`string`
`parent`	`object`	Groups of organization members that gives permissions on specified repositories.
`members_count`	`integer`
`html_url`	`string`
`slug`	`string`
`privacy`	`string`	The level of privacy this team should have
`organization`	`object`	Organization Full
`members_url`	`string`
`node_id`	`string`
`repositories_url`	`string`
`url`	`string`	URL for the team
`updated_at`	`string`
`created_at`	`string`
`repos_count`	`integer`
`permission`	`string`	Permission that the team will have for its repositories
`ldap_dn`	`string`	Distinguished Name (DN) that team maps to within LDAP environment

Name	Accessible by	Required Params	Description
`get_legacy`	`SELECT`	`team_id`	Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the Get a team by name endpoint.
`delete_legacy`	`DELETE`	`team_id`	Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Delete a team endpoint. To delete a team, the authenticated user must be an organization owner or team maintainer. If you are an organization owner, deleting a parent team will delete all of its child teams as well.
`update_legacy`	`EXEC`	`team_id, data__name`	Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Update a team endpoint. To edit a team, the authenticated user must either be an organization owner or a team maintainer. Note: With nested teams, the `privacy` for parent teams cannot be `secret`.