> ## Documentation Index > Fetch the complete documentation index at: https://astronomer.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # List bundle versions > List the versions that a bundle has moved to, newest first. A rollback to an earlier version appears as a new entry. ## OpenAPI ````yaml /astro/api/v-1-labs/openapi.yaml get /organizations/{organizationId}/deployments/{deploymentId}/bundles/{bundleId}/versions openapi: 3.0.3 info: contact: {} description: >- Astro Labs API - Experimental endpoints for preview features, plus everything served under /v1. title: Astro Labs API version: v1.1 servers: - url: /labs/v1.1 security: - JWT: [] tags: - description: >- Canned-data placeholder used to exercise the labs epoch versioning surface. Real labs endpoints register their own tags. name: Example - description: >- The `organization` object contains the metadata and configurations of an Astro Organization. It does not include objects within the Organization, such as users and clusters. Make requests to `organization` endpoints to view and update high level settings for your Organization, including settings related to authentication and billing. To manage resources within an Organization, make requests to the endpoints related to those resources, such as `users`. See [Billing](https://astronomer.io/docs/astro/manage-billing), [Set up single sign-on](https://astronomer.io/docs/astro/configure-idp), and [Manage domains](https://astronomer.io/docs/astro/manage-domains). name: Organization - description: >- The `deployment` object represents an Astro Deployment, which is a hosted Airflow environment that is powered by all core Airflow components, including schedulers and workers. Make requests to the `deployment` object to create, update, or delete a Deployment or its computational resources. See [Deployment settings](https://astronomer.io/docs/astro/deployment-settings). name: Deployment - description: >- A `cluster` object represents an Astro cluster, which is a Kubernetes cluster that hosts the infrastructure required to run Deployments. Make requests to `cluster` endpoints to manage your standard and dedicated clusters. See [Create a dedicated cluster](https://astronomer.io/docs/astro/create-dedicated-cluster). name: Cluster - description: >- The `workspace` object represents an Astro Workspace, which is a collection of Deployments that can be accessed by a specific group of users. It contains metadata about a Workspace, but does not contain objects within the Workspace such as users and Deployments. Make requests to `workspace` endpoints to manage high level details about your Workspace. To manage resources within a Workspace, make requests to the endpoints related to those resources, such as `users`, and use the `workspaceIds` parameter to filter results by Workspace. See [Configure Workspaces](https://astronomer.io/docs/astro/manage-workspaces). name: Workspace - description: >- The `user` object represents a user account in your Astro Organization. Astro creates a new `user` object whenever you invite a user by email or add a user to Astro through an identity provider. The object contains all information about a user, including their personal information, roles, and login attempts. It doesn't include attributes for actions that the user completes after they log in, such as updating a Deployment. Make requests to `user` endpoints to manage permissions for existing users both at the Organization and Workspace level. To create new users, make requests to `invite` endpoints instead. name: User - description: >- The `team` object represents an Astro Team, which is a group of users that share the same permissions across your Organization and Workspaces. Make requests to `team` endpoints to create, update, and delete Teams across an Organization. See [Configure Teams on Astro](https://astronomer.io/docs/astro/manage-teams). name: Team - description: >- The `apitoken` object represents a single API token within your Organization. API tokens are used to authenticate automated tools and processes to your Organization. They have varying levels of access to your resources based on their Organization, Workspace, and Deployment roles. See [Workspace API tokens](workspace-api-tokens.md) and [Organization API tokens](organization-api-tokens.md). name: api-token x-group: API Token - name: allowed-ip-address-range x-group: Allowed IP Address Range - name: agent-token x-group: Agent Token - name: notification-channels x-group: Notification Channels paths: /organizations/{organizationId}/deployments/{deploymentId}/bundles/{bundleId}/versions: get: tags: - Bundle summary: List bundle versions description: >- List the versions that a bundle has moved to, newest first. A rollback to an earlier version appears as a new entry. operationId: ListBundleVersions parameters: - description: The ID of the Organization to which the Deployment belongs. in: path name: organizationId required: true schema: type: string - description: The Deployment's ID. in: path name: deploymentId required: true schema: type: string - description: The bundle's ID. in: path name: bundleId required: true schema: type: string - description: The number of results to skip before returning values. in: query name: offset schema: default: 0 minimum: 0 type: integer - description: The maximum number of results to return. in: query name: limit schema: default: 20 maximum: 1000 minimum: 0 type: integer responses: '200': content: application/json: schema: $ref: '#/components/schemas/BundleVersionsPaginated' description: OK '400': content: application/json: schema: $ref: '#/components/schemas/Error' description: Bad Request '401': content: application/json: schema: $ref: '#/components/schemas/Error' description: Unauthorized '403': content: application/json: schema: $ref: '#/components/schemas/Error' description: Forbidden '404': content: application/json: schema: $ref: '#/components/schemas/Error' description: Not Found '500': content: application/json: schema: $ref: '#/components/schemas/Error' description: Internal Server Error security: - JWT: [] components: schemas: BundleVersionsPaginated: properties: limit: description: The maximum number of versions in one page. type: integer offset: description: The offset of the current page of versions. type: integer totalCount: description: The total number of versions. type: integer versions: description: A list of versions in the current page, newest first. items: $ref: '#/components/schemas/BundleVersion' type: array required: - limit - offset - totalCount - versions type: object Error: properties: fieldErrors: description: >- FieldErrors carries one entry per failed request-validation constraint. Only present on 400 responses caused by request binding/validation. items: $ref: '#/components/schemas/FieldValidationError' type: array message: type: string requestId: type: string statusCode: maximum: 600 minimum: 400 type: integer required: - message - requestId - statusCode type: object BundleVersion: properties: action: description: The operation that moved the bundle to this version. enum: - DEPLOY - ROLLBACK example: DEPLOY type: string createdAt: description: >- The time when the bundle moved to this version in UTC, formatted as `YYYY-MM-DDTHH:MM:SSZ`. example: '2022-11-22T04:37:12Z' format: date-time type: string createdById: description: The ID of the subject that moved the bundle to this version. example: clvetru2w000201mowqwua63n type: string deployId: description: The ID of the deploy that moved the bundle to this version. example: clvetru2w000201mowqwua63n type: string description: description: The description of the deploy that moved the bundle to this version. example: My deploy description type: string previousVersion: description: >- The version the bundle was on before this one. Appears only if the bundle had a version. type: string version: description: The version the bundle moved to. type: string required: - action - createdAt - deployId - version type: object FieldValidationError: properties: code: type: string field: type: string message: type: string required: - code - field - message type: object securitySchemes: JWT: scheme: bearer type: http ````