---
title: "List GroupMembership items"
method: GET
path: "/api/v3/team/{team_id}/memberships/items"
tags: ["Team"]
---

# List GroupMembership items

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

## Request

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

List GroupMembership items.

## Path parameters

- `team_id` string, required

## Query parameters

- `createdAt.gt` string, datetime
- `createdAt.gte` string, datetime
- `createdAt.lt` string, datetime
- `createdAt.lte` string, datetime
- `id.anyOf` string[]
- `memberId.eq` string
- `modifiedAt.gt` string, datetime
- `modifiedAt.gte` string, datetime
- `modifiedAt.lt` string, datetime
- `modifiedAt.lte` string, datetime
- `nextToken` string
- `pageSize` integer
- `sort` 'createdAt:asc' | 'createdAt:desc' | 'modifiedAt:asc' | 'modifiedAt:desc'

## Response `200`

OK

- GroupMembershipPaginatedList
  - `items` GroupMembership[]
    - `__typename` string
    - `createdAt` string, datetime
    - `group` union
      - object: Represents a group of users within Benchling, typically corresponding to a company, department, or research group. Organizations provide a many-to-many relationship between users—each user can belong to multiple organizations, and each organization can have multiple users. Users are designated as either ADMIN (with management privileges) or MEMBER within the organization via `GroupMembership`. Organizations can own resources like Projects and Folders, and can contain Teams for finer-grained user grouping. Organizations also control access settings such as whether members can create personal ownables and what default policies apply to new resources. In the UI, organizations appear in user profiles and are used for sharing and access control throughout Benchling.
        - `__typename` string, required
        - `createdAt` string, datetime
        - `handle` string
        - `id` string
        - `memberships` string, uri
        - `modifiedAt` string, datetime
        - `name` string, nullable
      - object: 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, required
        - `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
    - `id` string
    - `member` PrincipalRef
      - `__typename` string
      - `id` string, api_id
    - `modifiedAt` string, datetime
    - `role` 'MEMBER' | 'ADMIN'
  - `nextToken` string, nullable

## 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/c9f087b98b8b?raw)