> ## Documentation Index
> Fetch the complete documentation index at: https://docs.advinservers.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List a team's members

> ### Overview

Lists team memberships, the owner and unanswered invitations without pagination. Use each membership's `id` with member endpoints. The owner is separate and has no membership or role. Expired invitations remain listed until withdrawn or resent; `has_expired` identifies them.

### Permissions

Requires the account permission `teams.read` (View teams).



## OpenAPI

````yaml https://console.advinservers.com/docs/openapi.json get /teams/{team}/members
openapi: 3.1.0
info:
  title: API reference
  version: 1.0.0
  description: >-
    Use this API to manage your team's servers, networks, backups, and other
    resources.


    ## Authentication


    Create an API key under **API Keys** and send it as a bearer token with
    every request:


    ```

    Authorization: Bearer {YOUR_API_KEY}

    Accept: application/json

    ```


    Copy the key when you create it. It cannot be shown again. Revoking a key
    takes effect immediately.


    ## Permissions


    Give each key only the permissions it needs. Every endpoint lists the
    required permission.


    Permissions cover servers and other resources in the key's team.


    ## Team scope


    A key can access resources in the team selected when it was created. This
    includes servers,

    snapshots, backups, firewall groups, images, SSH keys, scripts, networks and
    addresses.

    Resources in other teams return `404 Not Found`. Create a separate key for
    each team.


    The key determines the team for every request. Legacy keys that had no team
    are assigned

    to the account's first owned team.


    ## Actions that need the panel


    API keys cannot do the following, even with every permission. Sign in to the
    panel in a

    browser to do them:


    - Create, edit or revoke API keys

    - Edit the IP groups that restrict API keys

    - End signed-in sessions

    - Change two-factor authentication

    - Change the account's email address

    - Accept or decline team invitations

    - Switch or leave a team


    This keeps a leaked key from widening its own access or locking you out of
    your account.


    ## Source IP restrictions


    A key can be restricted to one or more IP groups. Requests from other
    addresses are rejected.


    ## Requests and responses


    Each endpoint lists its path, query, header, and body parameters. Examples
    use fictional data.


    Single records use JSON objects. Collections use JSON arrays unless the
    endpoint supports pagination. Timestamps use ISO 8601 in UTC.


    Error responses include `message`. Validation errors also include an
    `errors` object for each field. Each endpoint lists its status codes.


    ## Audit log


    Every API request, including reads, is recorded in the account audit log
    with the key that made it.
servers:
  - url: https://console.advinservers.com/api/v1/client
security:
  - http: []
tags:
  - name: Account
    description: Billing contact details and account setup progress.
  - name: Account activity
    description: Actions performed in the current team by people and API keys.
  - name: Servers
    description: >-
      Order and list servers, read their state and resource use, open a console,
      and control power.
  - name: Server settings
    description: >-
      Rename a server, rebuild it, and change its hardware, media, resolvers and
      credentials.
  - name: Backups
    description: Scheduled server copies stored separately from the server.
  - name: Snapshots
    description: >-
      Take, restore and move server snapshots. Snapshots are kept in snapshot
      storage that the team buys by the GiB.
  - name: Firewall groups
    description: Reusable sets of firewall rules, and the servers they apply to.
  - name: IP groups
    description: Reusable source address lists for firewall rules.
  - name: Server firewall
    description: >-
      Read default traffic policies and rules managed outside your firewall
      groups.
  - name: IP addresses
    description: Manage floating IPs and server address assignments.
  - name: Private networks
    description: Connect servers over a private network in the same location.
  - name: Reverse DNS
    description: Set the hostnames returned by IP address lookups.
  - name: DDoS protection
    description: Configure attack filtering for server addresses.
  - name: Bandwidth
    description: Buy extra bandwidth and share it between servers or location pools.
  - name: SSH keys
    description: Public keys the account can install on a server when it is built.
  - name: Setup scripts
    description: Scripts the account can run on a server when it is built.
  - name: ISO images
    description: ISO images you have downloaded, and the servers they are mounted on.
  - name: Server upgrades
    description: Change an existing server's plan.
  - name: Checkout
    description: Choose a payment method and pay for a purchase.
  - name: Invoices
    description: View and pay account invoices.
  - name: Billing
    description: Manage service renewals, payment methods and account credit.
  - name: Transfers
    description: Move resources between teams or transfer ownership.
  - name: Teams
    description: Manage the team assigned to your API key.
  - name: Team members
    description: Invite people and manage their team access.
  - name: Team roles
    description: Define the permissions granted to team members.
  - name: Team activity
    description: View actions performed in a team.
  - name: Support tickets
    description: >-
      Open, read, reply to and close support tickets. Tickets belong to the
      account holder and are not shared with team members.
paths:
  /teams/{team}/members:
    get:
      tags:
        - Team members
      summary: List a team's members
      description: >-
        ### Overview


        Lists team memberships, the owner and unanswered invitations without
        pagination. Use each membership's `id` with member endpoints. The owner
        is separate and has no membership or role. Expired invitations remain
        listed until withdrawn or resent; `has_expired` identifies them.


        ### Permissions


        Requires the account permission `teams.read` (View teams).
      operationId: client.teams.members.index
      parameters:
        - name: team
          in: path
          required: true
          description: The team UUID
          schema:
            type: string
            examples:
              - fbb31f5f-bd6f-4019-a3ed-1062a28f56f7
          example: fbb31f5f-bd6f-4019-a3ed-1062a28f56f7
      responses:
        '200':
          description: The record, as a JSON object. There is no envelope.
          content:
            application/json:
              schema:
                type: object
                examples:
                  - items:
                      - id: b80181be-bb65-4aca-9246-e7335f330a34
                        name: Barney Calhoun
                        email: barney.calhoun@blackmesa.example.com
                        role:
                          id: 18f11680-0831-4d41-9d71-824c99009cbf
                          name: Research Associate
                          is_system: false
                        joined_at: '2026-01-12T17:31:05+00:00'
                        created_at: '2026-01-12T17:31:05+00:00'
                        gravatar_url: >-
                          https://www.gravatar.com/avatar/52fe79725661c25ad4a3f683abc54c3a?s=64&d=404
                    owner:
                      name: Gordon Freeman
                      email: gordon.freeman@blackmesa.example.com
                      gravatar_url: >-
                        https://www.gravatar.com/avatar/6108e5fddd878d82e464d4282b011ed7?s=64&d=404
                    invitations:
                      - id: 72623989-f7f9-4390-87ec-80f42b04b793
                        email: isaac.kleiner@blackmesa.example.com
                        team:
                          id: fbb31f5f-bd6f-4019-a3ed-1062a28f56f7
                          name: Anomalous Materials
                        role:
                          id: 18f11680-0831-4d41-9d71-824c99009cbf
                          name: Research Associate
                        invited_by:
                          name: Gordon Freeman
                          email: gordon.freeman@blackmesa.example.com
                        expires_at: '2026-09-16T10:05:37+00:00'
                        has_expired: false
                        created_at: '2026-09-13T10:05:37+00:00'
                properties:
                  items:
                    type: array
                    description: The memberships, by name.
                    examples:
                      - - id: b80181be-bb65-4aca-9246-e7335f330a34
                          name: Barney Calhoun
                          email: barney.calhoun@blackmesa.example.com
                          role:
                            id: 18f11680-0831-4d41-9d71-824c99009cbf
                            name: Research Associate
                            is_system: false
                          joined_at: '2026-01-12T17:31:05+00:00'
                          created_at: '2026-01-12T17:31:05+00:00'
                          gravatar_url: >-
                            https://www.gravatar.com/avatar/52fe79725661c25ad4a3f683abc54c3a?s=64&d=404
                    items:
                      $ref: '#/components/schemas/TeamMemberData'
                  owner:
                    description: >-
                      The account the team belongs to, which is never one of the
                      memberships above.
                    examples:
                      - name: Gordon Freeman
                        email: gordon.freeman@blackmesa.example.com
                        gravatar_url: >-
                          https://www.gravatar.com/avatar/6108e5fddd878d82e464d4282b011ed7?s=64&d=404
                    allOf:
                      - $ref: '#/components/schemas/TeamOwnerData'
                  invitations:
                    type: array
                    description: Offers that have not been answered, newest first.
                    examples:
                      - - id: 72623989-f7f9-4390-87ec-80f42b04b793
                          email: isaac.kleiner@blackmesa.example.com
                          team:
                            id: fbb31f5f-bd6f-4019-a3ed-1062a28f56f7
                            name: Anomalous Materials
                          role:
                            id: 18f11680-0831-4d41-9d71-824c99009cbf
                            name: Research Associate
                          invited_by:
                            name: Gordon Freeman
                            email: gordon.freeman@blackmesa.example.com
                          expires_at: '2026-09-16T10:05:37+00:00'
                          has_expired: false
                          created_at: '2026-09-13T10:05:37+00:00'
                    items:
                      $ref: '#/components/schemas/TeamInvitationData'
                required:
                  - items
                  - owner
                  - invitations
        '401':
          description: >-
            The key was missing, malformed, revoked, or belongs to an account
            that no longer exists.
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    examples:
                      - Unauthenticated.
                required:
                  - message
        '403':
          description: >-
            Access denied. Check the key's team, permissions and allowed IP
            addresses. Some actions, such as managing API keys, require a
            browser session. The response message explains the reason.
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    examples:
                      - >-
                        This API key is not allowed to do that in this team. It
                        needs the "snapshot.delete" permission.
                required:
                  - message
        '404':
          description: >-
            The resource was not found in the selected team. Resources in
            another account or team also return 404.
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    examples:
                      - Not found.
                required:
                  - message
        '429':
          description: >-
            Too many requests. The `Retry-After` header says how many seconds to
            wait. Limits are per account, so several keys on one account share
            them.
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    examples:
                      - Too Many Attempts.
                required:
                  - message
components:
  schemas:
    TeamMemberData:
      type: object
      description: A team member and their assigned role.
      examples:
        - id: b80181be-bb65-4aca-9246-e7335f330a34
          name: Barney Calhoun
          email: barney.calhoun@blackmesa.example.com
          role:
            id: 18f11680-0831-4d41-9d71-824c99009cbf
            name: Research Associate
            is_system: false
          joined_at: '2026-01-12T17:31:05+00:00'
          created_at: '2026-01-12T17:31:05+00:00'
          gravatar_url: >-
            https://www.gravatar.com/avatar/52fe79725661c25ad4a3f683abc54c3a?s=64&d=404
      properties:
        id:
          type: string
          description: The id ID.
          examples:
            - b80181be-bb65-4aca-9246-e7335f330a34
        name:
          type:
            - string
            - 'null'
          description: The name shown to customers.
          examples:
            - Barney Calhoun
        email:
          type:
            - string
            - 'null'
          description: The email address.
          examples:
            - barney.calhoun@blackmesa.example.com
        role:
          description: The value of `role`.
          examples:
            - id: 18f11680-0831-4d41-9d71-824c99009cbf
              name: Research Associate
              is_system: false
          anyOf:
            - $ref: '#/components/schemas/TeamRoleSummaryData'
            - type: 'null'
        joined_at:
          type:
            - string
            - 'null'
          description: The date and time for joined at, in UTC.
          examples:
            - '2026-01-12T17:31:05+00:00'
        created_at:
          type:
            - string
            - 'null'
          description: The date and time for created at, in UTC.
          examples:
            - '2026-01-12T17:31:05+00:00'
        gravatar_url:
          type:
            - string
            - 'null'
          description: The value of `gravatar_url`.
          examples:
            - >-
              https://www.gravatar.com/avatar/52fe79725661c25ad4a3f683abc54c3a?s=64&d=404
      required:
        - id
        - name
        - email
        - role
        - joined_at
        - created_at
        - gravatar_url
      title: TeamMemberData
    TeamOwnerData:
      type: object
      description: The account that owns a team.
      examples:
        - name: Gordon Freeman
          email: gordon.freeman@blackmesa.example.com
          gravatar_url: >-
            https://www.gravatar.com/avatar/6108e5fddd878d82e464d4282b011ed7?s=64&d=404
      properties:
        name:
          type:
            - string
            - 'null'
          description: The name shown to customers.
          examples:
            - Gordon Freeman
        email:
          type:
            - string
            - 'null'
          description: The email address.
          examples:
            - gordon.freeman@blackmesa.example.com
        gravatar_url:
          type:
            - string
            - 'null'
          description: The value of `gravatar_url`.
          examples:
            - >-
              https://www.gravatar.com/avatar/6108e5fddd878d82e464d4282b011ed7?s=64&d=404
      required:
        - name
        - email
        - gravatar_url
      title: TeamOwnerData
    TeamInvitationData:
      type: object
      description: >-
        An offer of a place in a team, waiting for the invited account to
        answer.
      examples:
        - id: 72623989-f7f9-4390-87ec-80f42b04b793
          email: isaac.kleiner@blackmesa.example.com
          team:
            id: fbb31f5f-bd6f-4019-a3ed-1062a28f56f7
            name: Anomalous Materials
          role:
            id: 18f11680-0831-4d41-9d71-824c99009cbf
            name: Research Associate
          invited_by:
            name: Gordon Freeman
            email: gordon.freeman@blackmesa.example.com
          expires_at: '2026-09-16T10:05:37+00:00'
          has_expired: false
          created_at: '2026-09-13T10:05:37+00:00'
      properties:
        id:
          type: string
          description: The id ID.
          examples:
            - 72623989-f7f9-4390-87ec-80f42b04b793
        email:
          type: string
          description: >-
            The address as it was invited. Kept rather than read back off the
            account so the row still reads correctly if the account has changed
            its email since.
          examples:
            - isaac.kleiner@blackmesa.example.com
        team:
          description: The destination team UUID.
          examples:
            - id: fbb31f5f-bd6f-4019-a3ed-1062a28f56f7
              name: Anomalous Materials
          anyOf:
            - $ref: '#/components/schemas/TeamInvitationTeamData'
            - type: 'null'
        role:
          description: The value of `role`.
          examples:
            - id: 18f11680-0831-4d41-9d71-824c99009cbf
              name: Research Associate
          anyOf:
            - $ref: '#/components/schemas/TeamInvitationRoleData'
            - type: 'null'
        invited_by:
          description: The value of `invited_by`.
          examples:
            - name: Gordon Freeman
              email: gordon.freeman@blackmesa.example.com
          anyOf:
            - $ref: '#/components/schemas/TeamInviterData'
            - type: 'null'
        expires_at:
          type:
            - string
            - 'null'
          description: When this action or checkout expires, in UTC.
          examples:
            - '2026-09-16T10:05:37+00:00'
        has_expired:
          type: boolean
          description: Whether the resource has expired.
          examples:
            - false
        created_at:
          type:
            - string
            - 'null'
          description: The date and time for created at, in UTC.
          examples:
            - '2026-09-13T10:05:37+00:00'
      required:
        - id
        - email
        - team
        - role
        - invited_by
        - expires_at
        - has_expired
        - created_at
      title: TeamInvitationData
    TeamRoleSummaryData:
      type: object
      description: >-
        A role named on a row that is about something else: the team you hold it
        in, or the member who holds it.
      examples:
        - id: 18f11680-0831-4d41-9d71-824c99009cbf
          name: Research Associate
          is_system: false
      properties:
        id:
          type: string
          description: The id ID.
          examples:
            - 18f11680-0831-4d41-9d71-824c99009cbf
        name:
          type: string
          description: The name shown to customers.
          examples:
            - Research Associate
        is_system:
          type: boolean
          description: Whether the resource is system.
          examples:
            - false
      required:
        - id
        - name
        - is_system
      title: TeamRoleSummaryData
    TeamInvitationTeamData:
      type: object
      description: The team named in an invitation.
      examples:
        - id: fbb31f5f-bd6f-4019-a3ed-1062a28f56f7
          name: Anomalous Materials
      properties:
        id:
          type: string
          description: The id ID.
          examples:
            - fbb31f5f-bd6f-4019-a3ed-1062a28f56f7
        name:
          type: string
          description: The name shown to customers.
          examples:
            - Anomalous Materials
      required:
        - id
        - name
      title: TeamInvitationTeamData
    TeamInvitationRoleData:
      type: object
      description: The role on offer in an invitation.
      examples:
        - id: 18f11680-0831-4d41-9d71-824c99009cbf
          name: Research Associate
      properties:
        id:
          type: string
          description: The id ID.
          examples:
            - 18f11680-0831-4d41-9d71-824c99009cbf
        name:
          type: string
          description: The name shown to customers.
          examples:
            - Research Associate
      required:
        - id
        - name
      title: TeamInvitationRoleData
    TeamInviterData:
      type: object
      description: >-
        Whoever sent an invitation, so the person deciding whether to accept it
        can see a name they recognise rather than only the team's.
      examples:
        - name: Gordon Freeman
          email: gordon.freeman@blackmesa.example.com
      properties:
        name:
          type: string
          description: The name shown to customers.
          examples:
            - Gordon Freeman
        email:
          type: string
          description: The email address.
          examples:
            - gordon.freeman@blackmesa.example.com
      required:
        - name
        - email
      title: TeamInviterData
  securitySchemes:
    http:
      type: http
      description: >-
        Your API key, sent as a bearer token. Create one in the control panel
        under API Keys, give it only the permissions the integration needs, and
        copy it when it is created. It cannot be shown again. Each key is
        restricted to one owned team. The key determines the team for every
        request.
      scheme: bearer

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.