> ## Documentation Index > Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt > Use this file to discover all available pages before exploring further. # List teams for an event occurrence > Returns a paginated list of the teams of an event occurrence, each with its current members as participant ids and its captain. Teams created by a team import carry the `externalTeamId` you sent, so you can check an import against what you sent; filter by `externalTeamId` to read one team back. ## OpenAPI ````yaml /openapi.json get /v0/event-occurrences/{id}/teams openapi: 3.1.0 info: title: Let's Do This API version: 0.1.0 description: > The full reference — getting started, pagination, error responses, rate limits and the changelog — lives at [partner-help.letsdothis.com/api-reference](https://partner-help.letsdothis.com/api-reference/overview). This page is the interactive OpenAPI view of the same specification. # Authentication Create an API key from **Settings** → **Credentials** in your Let's Do This account and send it as a bearer token: ```bash curl --request GET \ --url "https://api.letsdothis.com/v0/participants" \ --header "Authorization: Bearer YOUR-API-KEY" ``` Keep the key secret: it identifies your organization, so do not ship it in a website or native app. If a key is exposed, revoke it from the same section and create a replacement. # OpenAPI schema Download the [OpenAPI schema](https://api.letsdothis.com/documentation/json) to use with Postman or an OpenAPI client generator. servers: - url: https://api.letsdothis.com description: Production - url: https://api.staging.letsdothis.com description: Staging security: - bearerAuth: [] tags: - name: Events x-group: Events description: Events that participants can register for. - name: EventOccurrences x-group: Event occurrences description: >- Event occurrences scoped to the organizer associated with your Public API credentials. Unlike the public Events catalog, results are limited to your own events. - name: Races x-group: Races description: >- Races within an event occurrence. An event occurrence may have one or more races, for example a 5K and a 10K within the same race day. - name: Tickets x-group: Tickets description: Tickets that are available for events. - name: BookingForms x-group: Booking forms description: >- Booking forms define the questions a booker answers when registering for a ticket. A ticket usually references a single booking form, so expect zero or one, while a booking form may be shared across multiple tickets. - name: BookingFormFields x-group: Booking form fields description: >- Booking form fields are the individual questions on a booking form — their type, label, options, and whether an answer is required. A field can be reused across multiple forms. - name: Bookings x-group: Bookings description: >- Bookings are the transaction record for a registration. A booking may contain one or more participants (entries). - name: Membership x-group: Memberships description: >- Membership schemes, purchased policies and the seats on them, owned by your organizer. Policies are billing contracts; a seat is one person's place on a policy. - name: Participant x-group: Participants description: Participants are users who successfully booked an event. - name: LineItem x-group: Line items description: Financial details related to individual items within transactions. - name: AddOns x-group: Add-ons description: >- Organizer-owned products that can be purchased and allocated to participants. Imported products retain stable external identities. - name: DiscountCodes x-group: Discount codes description: >- Discount codes participants enter at checkout to reduce the price of a booking. - name: Credits x-group: Credits description: >- Credits are balances participants can spend at checkout, identified by their email address. - name: Referrals x-group: Referrals description: >- Referral programs, the referrers registered on them, and asynchronous imports of historical referrals. - name: Teams x-group: Teams description: >- Teams group participants of an event occurrence under a team program. Teams can be imported for participants whose bookings were imported. - name: Application x-group: Applications description: >- Applications are created when a user applies for tickets that are set up to require an application process, such as balloted or "Good For Age" entries. - name: Partner x-group: Partners description: >- Partners that were created by the organization who can have Reserved Entries assigned to them. - name: ReservedEntries x-group: Reserved entries description: >- Reserved Entries are entries that are reserved for a partner. After being assigned, the partner can then allocate these entries to participants. - name: Timing x-group: Timing description: >- Timing providers push bib numbers and bib-pack shipments back to Let's Do This for the startlist entries they received. Available to select timing partners only. - name: Identity x-group: API key description: >- What your API key can reach. Available to every key, including scoped ones. paths: /v0/event-occurrences/{id}/teams: get: tags: - Teams summary: List teams for an event occurrence description: >- Returns a paginated list of the teams of an event occurrence, each with its current members as participant ids and its captain. Teams created by a team import carry the `externalTeamId` you sent, so you can check an import against what you sent; filter by `externalTeamId` to read one team back. parameters: - schema: type: integer minimum: 1 maximum: 500 in: query name: page[size] required: false description: >- The number of entries to return per page. Range between 1 - 500, defaults to 100. - schema: type: string in: query name: page[after] required: false description: >- Accepts an existing page cursor to return results after it. For more details see the definition of PageCursor in the response. - schema: type: string in: query name: page[before] required: false description: >- Accepts an existing page cursor to return results before it. For more details see the definition of PageCursor in the response. - schema: type: string minLength: 1 maxLength: 255 in: query name: externalTeamId required: false description: Filter to the team you imported with this external team id. - schema: type: string example: '12345678901' in: path name: id required: true description: The ID of the event occurrence to query by. responses: '200': description: Default Response content: application/json: schema: $ref: '#/components/schemas/PagedTeams' '400': description: Bad request content: application/json: schema: description: Bad request type: object properties: statusCode: type: number enum: - 400 error: type: string message: type: string '404': description: Not found content: application/json: schema: description: Not found type: object properties: statusCode: type: number enum: - 404 error: type: string message: type: string components: schemas: PagedTeams: title: PagedTeams type: object properties: data: type: array items: $ref: '#/components/schemas/Team' page: $ref: '#/components/schemas/PageCursor' required: - data - page additionalProperties: false description: A paginated list of an event occurrence's teams. Team: title: Team type: object properties: id: type: string description: 'The team''s id: the `teamId` of a team import result.' externalTeamId: type: - string - 'null' description: >- Your id for the team when it was created by a team import, otherwise `null`. teamName: type: string teamNumber: type: - number - 'null' description: The team's number within the event occurrence, when it has one. teamProgramId: type: string description: The team program the team belongs to. isPrivate: type: boolean description: Private teams can only be joined with their invite code. memberParticipantIds: type: array items: type: string description: >- The team's current members, as participant ids. Empty when it has none. captainParticipantId: type: - string - 'null' description: The captain when the captain is a participant, otherwise `null`. nonParticipatingCaptain: anyOf: - $ref: '#/components/schemas/TeamNonParticipatingCaptain' - type: 'null' description: >- The captain when the captain is not taking part in the event, otherwise `null`. createdAt: $ref: '#/components/schemas/ISODate' required: - id - externalTeamId - teamName - teamNumber - teamProgramId - isPrivate - memberParticipantIds - captainParticipantId - nonParticipatingCaptain - createdAt additionalProperties: false description: >- A team of an event occurrence. The fields match a team import row, so an imported team can be compared with what was sent. PageCursor: title: PageCursor type: object properties: totalResults: type: number description: The total number of results available. first: type: string description: The cursor for the first page of results. last: type: string description: The cursor for the last page of results. prev: type: string description: The cursor for the previous page of results. next: type: string description: The cursor for the next page of results. required: - totalResults - first - last - prev - next additionalProperties: false description: >- **Cursor details for pagination**. - In scenarios with large amounts of data, it's common to return only a subset of data in a single request, known as a "page". - Most API responses include two objects: a 'data' object with the query results, and a 'PageCursor' object detailing the current page. - Cursors can be used to navigate to earlier or later pages in the set of results. For instance, passing the 'next' cursor from 'PageCursor' fetches the next set of results. - Cursors are base64 encoded strings. example: totalResults: 506 first: >- eyJpZCI6IjYzOTljMjAwMTVkNjBhZTNmZjI4ZjI0YyIsInVwZGF0ZWRBdCI6IjIwMjItMTItMTRUMTI6MzA6NTkuMjE3WiJ9 last: >- eyJpZCI6IjY1NGNkZDIxZDlhMTU3ODdiNzFkMTM0YSIsInVwZGF0ZWRBdCI6IjIwMjMtMTEtMTNUMTU6MTE6MTIuNzI0WiJ9 prev: '' next: >- eyJpZCI6IjY0NzBkNTkwM2RjOWE5OWJhMTA0Y2ZhYiIsInVwZGF0ZWRBdCI6IjIwMjMtMTEtMTNUMTU6MTE6MTIuNjE4WiJ9 TeamNonParticipatingCaptain: title: TeamNonParticipatingCaptain type: object properties: fullName: type: string emailAddress: type: - string - 'null' required: - fullName - emailAddress additionalProperties: false description: A team captain who is not taking part in the event. ISODate: title: ISODate type: string description: >- Represents a date and time in ISO 8601 format as a string. The string should follow the format `YYYY-MM-DDTHH:mm:ss.sssZ`, where: - `YYYY`: Four-digit year - `MM`: Two-digit month (01-12) - `DD`: Two-digit day of the month (01-31) - `T`: Delimiter indicating the start of the time component - `HH`: Two-digit hour in 24-hour format (00-23) - `mm`: Two-digit minutes (00-59) - `ss.sss`: Seconds with milliseconds (00.000-59.999) - `Z`: UTC timezone designator **Example:** To represent 11:30 AM on May 8th, 2026, the value would be: `"2026-05-08T11:30:00.000Z"`. example: '2026-05-08T11:30:00.000Z' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.