> ## 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 pipeline caches > The same listing addressed by application: the keyed cache volumes of the pipeline repository the application is connected to, most recently used first by keyset. Requires pipelines.read. Read-only. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json get /api/v1/org/applications/{application_id}/pipeline-caches openapi: 3.1.0 info: title: FastAPI version: 0.1.0 servers: - url: https://platform.ankra.app security: [] tags: - name: Organisation IAM description: >- Custom organisation roles and scoped role assignments for member and service-account identities. - 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: AWS Clusters description: >- Provision and manage self-managed k3s / kubeadm clusters on AWS EC2 in your own VPC. - name: Ankra Cloud Clusters description: >- Provision and manage self-managed kubeadm / k3s clusters on Ankra Cloud servers: a private network, a NAT router and a bastion per 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: Pipelines description: >- Pipeline definitions, the approval of the authority they declare, and the caches pipelines keep between runs. - name: Deploy Targets description: >- Environments, the hosts registered to receive deployments, and the releases deployed to them. - name: Backups description: >- Backup vaults, restore points, protection posture and captures for stacks and application deployments; a completed capture is not a verified restore. - name: Stack Profiles description: Reusable stack definitions, their versions and sharing. - name: Services description: >- Versioned service packages and explicit sharing. Runtime admission is separate from publication. - 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 Management description: >- Customer agent lifecycle, authenticated identity and organisation automation controls. - 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 Remediation description: >- The organisation's auto-remediation policy: what the AI lanes may fix by themselves, and who approves the rest. - 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: Decisions description: >- The decision ledger behind the Security and Cost queues: proposals a surface computed, the approve and set-aside decisions people took on them, and the receipts of running them. - 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: AWS Credentials description: >- AWS credentials: access keys or CloudFormation-onboarded STS roles for cost, EKS and self-managed provisioning. - name: Ankra Cloud Credentials description: >- Ankra Cloud API tokens, shared by the self-managed and managed Ankra Cloud lanes. - 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: Object Storage Buckets description: >- Buckets Ankra creates and manages on an organisation's own provider credentials. - name: DNS description: DNS zones and records, including custom organisation zones. - name: Cloudflare description: Cloudflare domains and the credentials behind them. - name: Avura description: >- The linked Avura organization, the domains it shares with Ankra Platform, and their DNS records. - 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. - name: AI Settings description: Organisation AI provider, model catalog and per-function model settings paths: /api/v1/org/applications/{application_id}/pipeline-caches: get: tags: - Pipelines summary: List an application's pipeline caches description: >- The same listing addressed by application: the keyed cache volumes of the pipeline repository the application is connected to, most recently used first by keyset. Requires pipelines.read. Read-only. operationId: listApplicationPipelineCachesToken parameters: - name: application_id in: path required: true schema: type: string format: uuid - name: cursor in: query required: false schema: type: string description: The next_cursor of the previous page. - name: limit in: query required: false schema: type: integer minimum: 1 maximum: 100 default: 50 responses: '200': description: One page of caches. content: application/json: schema: $ref: '#/components/schemas/PipelineCachePage' '401': description: Authentication required '403': description: Missing pipelines.read '404': description: The application has no pipeline repository connected '422': description: Malformed application id, cursor or limit '500': description: Internal error security: - BearerAuth: [] components: schemas: PipelineCachePage: type: object additionalProperties: false required: - caches - retention_days - next_cursor properties: caches: type: array items: $ref: '#/components/schemas/PipelineCache' retention_days: type: integer minimum: 1 maximum: 365 description: >- The organisation's cache retention in days (ci_cache_retention_days), the number every expires_at on the page was derived from. next_cursor: type: - string - 'null' description: Pass as cursor to read the next page; null on the last page. PipelineCache: type: object additionalProperties: false required: - id - organisation_id - repository_id - cluster_id - cluster_name - key - mount_path - trust - size - storage_class - claim_name - created_at - last_used_at - expires_at - state properties: id: type: string format: uuid organisation_id: type: string format: uuid repository_id: type: string format: uuid cluster_id: type: string format: uuid description: The cluster the cache's volume lives on. cluster_name: type: string description: >- That cluster's name; empty when the cluster no longer exists in the organisation. key: type: string description: >- The cache key a stage declared, after the platform's own templating. A hashFiles(...) call is carried verbatim. mount_path: type: string description: Where the cache is mounted in the step. trust: type: string enum: - default_branch - branch description: >- The scope the cache is isolated to: default_branch for runs of the repository's default branch, branch for every other run. The two never share a volume. size: type: string description: >- The storage the volume was requested with, as a Kubernetes quantity such as 5Gi. storage_class: type: string description: >- The StorageClass the volume was requested with; empty for the cluster's default. claim_name: type: string description: >- The PersistentVolumeClaim a step mounts. Two caches may name one claim when a restore_keys match aliased a new key onto an existing volume. created_at: type: string format: date-time last_used_at: type: string format: date-time description: When a step last resolved the cache. expires_at: type: string format: date-time description: >- last_used_at plus the organisation's cache retention: the moment the retention sweep stops treating the cache as fresh. Each use moves it forward. state: type: string enum: - active - removing description: >- removing once the retention sweep has dispatched the volume's deletion to the cluster; active otherwise. securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.