> ## Documentation Index > Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt > Use this file to discover all available pages before exploring further. # List an application's deploy runs > List the deploy runs recorded for this application, newest first. application_deploy_run is written when the user presses Deploy and carries the cluster, the ordered roles and the stack name confirmed for each, so an application can show a deploy that is queued, in flight or failed without the browser having remembered its run id - which was previously the only way to reach one. The listing is capped at 50 runs and reports truncated=true when older runs exist beyond it. An unknown application answers 404 rather than an empty list. Browser session authentication only (no bearer twin). ## OpenAPI ````yaml https://platform.ankra.app/openapi.json get /org/applications/{application_id}/deploy-runs openapi: 3.1.0 info: title: FastAPI version: 0.1.0 servers: - url: https://platform.ankra.app security: [] tags: - name: Clusters description: Create, inspect and manage clusters, and the stacks deployed on them. - name: Managed Clusters description: Provider-managed control planes, driven through one common surface. - name: Imported Clusters description: Clusters that already existed and were connected to Ankra. - name: Cluster Access description: Kubeconfigs, service-account tokens and per-cluster access grants. - name: Kubernetes description: Read and act on the Kubernetes objects inside a cluster. - name: DigitalOcean Clusters description: Provision and manage DigitalOcean Kubernetes clusters. - name: Hetzner Clusters description: Provision and manage Hetzner Kubernetes clusters. - name: OVH Clusters description: Provision and manage OVH Kubernetes clusters. - name: Scaleway Clusters description: Provision and manage Scaleway Kapsule clusters. - name: UpCloud Clusters description: Provision and manage UpCloud Kubernetes clusters. - name: Applications description: Deploy, configure and observe applications across the fleet. - name: Stack Profiles description: Reusable stack definitions, their versions and sharing. - name: Charts description: Browse the chart catalogue behind stacks and addons. - name: Helm description: Helm registries, credentials and the charts they expose. - name: Executions description: Long-running platform executions and their jobs. - name: Operations description: Cancel in-flight cluster operations and their jobs. - name: Chat description: Conversational sessions, plans and confirmable actions. - name: AI Agent Runs description: Autonomous agent runs and their outcomes. - name: AI Tickets description: The AI ticket board, its sync connections and settings. - name: AI Playbooks description: Reusable playbooks the AI lanes execute. - name: AI Conditions description: Conditions that gate AI autonomy. - name: AI Engineering Handoffs description: Work the AI lanes escalate to a human engineer. - name: AI Environment description: The environment and base stacks AI demos deploy into. - name: Security description: Findings, advisories, SBOMs, compliance and posture. - name: Cost description: Cluster and fleet cost, rate cards and cost settings. - name: Billing description: Subscription and spend caps. - name: Organisation description: Members, invitations, audit logs and organisation settings. - name: Account Tokens description: Personal access tokens for the API and CLI. - name: Credentials description: The shared credential store. - name: Azure Credentials description: Azure credentials and SSH keys. - name: DigitalOcean Credentials description: DigitalOcean credentials and SSH keys. - name: Hetzner Credentials description: Hetzner credentials and SSH keys. - name: OVH Credentials description: OVH credentials and SSH keys. - name: Scaleway Credentials description: Scaleway credentials. - name: UpCloud Credentials description: UpCloud credentials and SSH keys. - name: Data Source Credentials description: Credentials for metrics and log sources. - name: DNS Credentials description: Credentials for DNS providers. - name: DNS description: DNS zones and records, including custom organisation zones. - name: Cloudflare description: Cloudflare domains and the credentials behind them. - name: Variables description: Organisation- and cluster-scoped variables. - name: SOPS description: Encrypt and decrypt values with the organisation SOPS config. - name: Alerts description: Alert integrations and ingest credentials. - name: Notifications description: Notification routes and their delivery targets. - name: Support description: Support tickets. paths: /org/applications/{application_id}/deploy-runs: get: tags: - Applications summary: List an application's deploy runs description: >- List the deploy runs recorded for this application, newest first. application_deploy_run is written when the user presses Deploy and carries the cluster, the ordered roles and the stack name confirmed for each, so an application can show a deploy that is queued, in flight or failed without the browser having remembered its run id - which was previously the only way to reach one. The listing is capped at 50 runs and reports truncated=true when older runs exist beyond it. An unknown application answers 404 rather than an empty list. Browser session authentication only (no bearer twin). operationId: list_application_deploy_runs parameters: - in: path name: application_id required: true schema: type: string title: Application Id responses: '200': content: application/json: schema: $ref: '#/components/schemas/ListDeployRunsResponse' description: Successful Response '404': content: application/json: schema: $ref: '#/components/schemas/DemoDetailError' description: Not found ("Application not found") '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Validation Error components: schemas: ListDeployRunsResponse: description: An application's deploy runs, newest first. properties: deploy_runs: items: $ref: '#/components/schemas/DeployRunSummary' title: Deploy Runs type: array truncated: title: Truncated type: boolean description: >- True when older runs exist beyond the 50 listed. A capped listing that did not say so would read as the application's whole deploy history. required: - deploy_runs - truncated title: ListDeployRunsResponse type: object DemoDetailError: description: >- The FastAPI-style detail envelope the demo routes use for 400/403/404/409/502 responses. properties: detail: type: string required: - detail type: object HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object DeployRunSummary: description: One recorded deploy attempt for an application. properties: id: title: Id type: string cluster_id: type: string title: Cluster Id cluster_name: anyOf: - type: string - type: 'null' title: Cluster Name description: >- The cluster's name, or null when the cluster row could not be read. Absent rather than empty so it cannot be mistaken for a cluster with no name. cluster_deleted: title: Cluster Deleted type: boolean description: >- True when the run's cluster has since been soft deleted. The run is still listed - it is the record of what was deployed - but a deployment on a decommissioned cluster is a different fact from one on a live cluster. status: title: Status type: string description: pending, running, succeeded, or failed. message: anyOf: - type: string - type: 'null' title: Message description: Why the run failed, when it did. created_at: type: string title: Created At updated_at: title: Updated At type: string finished_at: anyOf: - type: string - type: 'null' title: Finished At description: RFC 3339, or null while the run has not settled. roles: items: $ref: '#/components/schemas/DeployRunRole' title: Roles type: array required: - id - cluster_id - cluster_name - cluster_deleted - status - message - created_at - updated_at - finished_at - roles title: DeployRunSummary type: object ValidationError: properties: loc: items: anyOf: - type: string - type: integer title: Location type: array msg: title: Message type: string type: title: Error Type type: string required: - loc - msg - type title: ValidationError type: object DeployRunRole: properties: role: type: string title: Role position: title: Position type: integer draft_id: title: Draft Id type: string stack_name: title: Stack Name type: string created_stack_name: anyOf: - type: string - type: 'null' title: Created Stack Name description: The name the cluster used, present once the stack has been created. operation_id: anyOf: - type: string - type: 'null' title: Operation Id status: title: Status type: string description: pending, creating, waiting, stalled, deployed, or failed. message: anyOf: - type: string - type: 'null' title: Message description: Why the role stopped, when it did. required: - role - position - draft_id - stack_name - created_stack_name - operation_id - status - message title: DeployRunRole type: object ````