---
title: "Get Team by ID"
method: GET
path: "/api/v3/team/{team_id}"
tags: ["Team"]
---

# Get Team by ID

`GET /api/v3/team/{team_id}`

## Request

- Base URL: `https://{tenant_name}.benchling.com`
- URL: `https://{tenant_name}.benchling.com/api/v3/team/{team_id}`
- Auth: HTTP bearer

Get a single Team by ID.

## Path parameters

- `team_id` string, required

## Query parameters

- `returning` string[]
- `omit` string[]

## Response `200`

OK

- Team: Represents a subgroup of users within an `Organization`, enabling finer-grained user management and data sharing. Teams belong to exactly one organization, and users may only join a team if they are already members of that team's parent organization. Each team member has either ADMIN or MEMBER role (see `GroupMembership`): admins can manage team membership, while members receive standard access. Unlike Organizations, teams cannot directly own Projects or Folders—they are used for collaboration and access control purposes. Teams can be configured with `provisionedCapabilities` to grant specific Benchling capabilities to members upon joining. The `membersAreAdministratorsOfSchemas` flag controls whether team members can create and update automation, result, and request schemas.
  - `__typename` string
  - `createdAt` string, datetime
  - `description` string
  - `id` string
  - `membersAreAdministratorsOfSchemas` boolean: Team members can create and update automation, result, and request schemas.
  - `memberships` string, uri
  - `modifiedAt` string, datetime
  - `name` string
  - `organization` OrganizationRef
    - `__typename` string
    - `id` string, api_id

## Other responses

- `400`: Bad Request
- `403`: Forbidden
- `404`: Not Found
- `429`: Too Many Requests
- `500`: Internal Server Error

---

[API](https://skmtc.dev/benchling/apis/benchling-api.md) - [All operations](https://skmtc.dev/benchling/apis/benchling-api/llms.txt) - [OpenAPI document](https://skmtc.dev/benchling/apis/benchling-api/revisions/3873a10bf7b8?raw)