> ## Documentation Index > Fetch the complete documentation index at: https://docs.zuddl.com/llms.txt > Use this file to discover all available pages before exploring further. # Get all teams > Returns the teams in your Zuddl organization that the caller can create events in. A user token sees the teams that user belongs to; an API key, which has no team membership, sees every active team in the organization. Use the returned id as teamId when creating an event. Required API key scopes: `READ` ## OpenAPI ````yaml https://api.prod.zuddl.com/api/v3/api-docs/api-product get /v1/teams openapi: 3.1.0 info: title: Zuddl API Documentation description: >- Zuddl RESTful APIs let you interact with the Zuddl platform and take action for your event or webinar. They let you add attendees, get attendee details, get event details, and more. The API response is returned in JSON, which your systems can easily consume. The API parameters allow you to customize the response using filters, sorting, pagination, and other parameters. Parameter values should be percent-encoded (URL-encoded) to ensure correct transmission, especially if they contain special characters such as spaces, semi-colons, or slashes. # Rate limits | Metrics | Value | | --- | --- | | Requests/second | 10 | | Burst or no. of concurrent calls allowed | 100 requests | | Total quota | 10000 requests/day | version: '1.0' servers: - url: https://api.zuddl.com/ security: - api_key: [] tags: - name: Events description: API endpoints for managing events - name: Attendees description: >- The attendee APIs let you add and retrieve attendee in a particular event type. - name: Sessions description: API endpoints for managing event sessions - name: Speakers description: API endpoints for managing event speakers - name: Sponsors description: API endpoints for managing event sponsors - name: Teams description: API endpoints for reading the teams events can be created in - name: Locations description: API endpoints for managing event locations paths: /v1/teams: get: tags: - Teams summary: Get all teams description: >- Returns the teams in your Zuddl organization that the caller can create events in. A user token sees the teams that user belongs to; an API key, which has no team membership, sees every active team in the organization. Use the returned id as teamId when creating an event. Required API key scopes: `READ` operationId: getTeams parameters: - name: q in: query required: false schema: type: string - name: page in: query required: false schema: type: integer format: int32 - name: size in: query required: false schema: type: integer format: int32 responses: '200': description: List of teams retrieved successfully content: application/json: schema: $ref: >- #/components/schemas/org.events.app.domain.api_product.organization.team.dtos.TeamDetailsPage '400': description: Bad Request content: '*/*': schema: oneOf: - type: string - $ref: >- #/components/schemas/org.events.app._internal._response.ValidationErrorResponse '401': description: Unauthorized content: application/json: schema: $ref: >- #/components/schemas/org.events.app._internal._response.v1.ApiErrorResponse components: schemas: org.events.app.domain.api_product.organization.team.dtos.TeamDetailsPage: properties: pagination: $ref: >- #/components/schemas/org.events.app.domain.api_product.dtos.PageResponse.Pagination data: type: array items: $ref: >- #/components/schemas/org.events.app.domain.api_product.organization.team.dtos.TeamDetails org.events.app._internal._response.ValidationErrorResponse: properties: message: type: string description: type: string code: type: string params: type: object additionalProperties: type: object validationErrors: type: array items: $ref: >- #/components/schemas/org.events.app._internal._response.ValidationError org.events.app._internal._response.v1.ApiErrorResponse: properties: timestamp: type: string format: date-time message: type: string description: type: string code: type: string params: type: object additionalProperties: type: object errors: type: object additionalProperties: type: string org.events.app.domain.api_product.dtos.PageResponse.Pagination: properties: next: type: string format: uri description: URI of the next page. Also indicates the presence of a next page. example: /{apiEndpoint}?page=3 current: type: string format: uri description: URI of the current page. example: /{apiEndpoint}?page=2 previous: type: string format: uri description: >- URI of the previous page. Also indicates the presence of a previous page. example: /{apiEndpoint}?page=1 org.events.app.domain.api_product.organization.team.dtos.TeamDetails: properties: kind: type: string url: type: string format: uri id: type: string format: uuid description: >- Unique identifier of the team. This is the value to pass as teamId when creating an event. example: 4fcebf73-3ddb-4fe6-b56d-5dd7dedb7c3d name: type: string description: Display name of the team example: Marketing isGeneral: type: boolean description: >- True for the organization's default team, which every member belongs to. Use it when no particular team is called for. example: false org.events.app._internal._response.ValidationError: properties: fieldName: type: string fieldMessage: type: string securitySchemes: api_key: type: apiKey description: Provide your API key secret in the `Authorization` header name: Authorization in: header ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.