> ## 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. # Start or reuse remediation runs for a security finding (browser session) > Opens or reuses the fix pull request per affected application repository (the image rebuild lane), starts or answers the live remediation run for each, and dispatches the pull request branch's head through Ankra Pipelines under the default branch's approved authority. Repeating the call reuses the live runs; nothing is approved, waived or accepted. The caller, a person through their session or their API token, is the one asking, so the organisation's AI autonomy pause and the application's keep_it_safe choice do not hold this start; they hold every step Ankra later takes on its own for the run, such as re-running its pipeline after an Ankra infrastructure error, which then stops the run at needs_human with the reason. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json post /org/security/findings/{finding_id}/remediations openapi: 3.1.0 info: title: Ankra Platform API version: v1 description: >- The Ankra platform HTTP contract. The /api/v1 surface is the public, bearer-authenticated API used by the Ankra CLI, MCP clients and automation; send a personal or service API token as `Authorization: Bearer `. Browser routes under /org and /chat are served on api.platform.ankra.app (each declares that server); they and /oauth/access authenticate with the ankra_session cookie, and mutations also require the X-Ankra-CSRF header. Every operation declares the credential it accepts, and no operation is served without one. This document is published deliberately: it describes the contract only and carries no organisation data or credentials. Report security issues to security@ankra.ai (see /.well-known/security.txt). servers: - url: https://platform.ankra.app security: - BearerAuth: [] tags: - name: Onboarding description: >- Generate a first website from a prompt and deploy it to a new organisation's cluster. - name: Access Gate description: >- Private service sign-in and membership checks for trusted Ankra proxy relays. - name: Canvas Datasets description: >- Read the fixed, named datasets canvas dashboards bind their charts, tables and stats to. - name: Canvases description: >- Keep dashboards and pages in the organisation's canvas library, with revision history, undo and pins. - name: Canvas Pages description: >- Publish a chat canvas artifact at a public pages address and take it down again. - name: Cloud Delegation description: >- Platform browser consent and organisation-bound connections for Ankra Cloud. - 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: Workspaces description: >- Personal workspaces on the organisation's CI pool where a repository's heavy commands run, and the repository profiles they are built from. - name: Deploy Targets description: >- Environments, the hosts registered to receive deployments, and the releases deployed to them. - name: Deploy Provenance description: >- Whether an application's deploys verify signed provenance from the organisation's own pipeline, the keys that provenance is signed with, and a dry-run that verifies images without deploying. - 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: AI Memory description: >- What the assistant has learned about you: your cross-session memories and learned profile. - name: MCP Servers description: >- Register the MCP servers the organisation's AI agents can call, choose their tools and grant them to roles. - 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: Usage description: >- What your organisation used of Ankra - vCPU-hours, playgrounds, managed services, hosted logs and metrics, and AI - per meter and period, with how completely it was measured and whether a published rate applies. - name: Billing description: Subscription and spend caps. - name: Organisation description: Members, invitations, audit logs and organisation settings. - name: Account description: >- Your own account: the contact email Ankra mails when it differs from your sign-in address. - 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: HPE Morpheus Credentials description: HPE Morpheus credentials and the capacity and quotas behind them. - name: OVH Credentials description: OVH credentials and SSH keys. - name: Proxmox Credentials description: Proxmox VE credentials and the capacity and quotas behind them. - 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: Secret Slots description: >- Store secrets in Vault and reference them by ${SECRET_SLOT:} sentinel instead of by value. - 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: /org/security/findings/{finding_id}/remediations: post: tags: - Security summary: Start or reuse remediation runs for a security finding (browser session) description: >- Opens or reuses the fix pull request per affected application repository (the image rebuild lane), starts or answers the live remediation run for each, and dispatches the pull request branch's head through Ankra Pipelines under the default branch's approved authority. Repeating the call reuses the live runs; nothing is approved, waived or accepted. The caller, a person through their session or their API token, is the one asking, so the organisation's AI autonomy pause and the application's keep_it_safe choice do not hold this start; they hold every step Ankra later takes on its own for the run, such as re-running its pipeline after an Ankra infrastructure error, which then stops the run at needs_human with the reason. operationId: start_security_remediation parameters: - in: path name: finding_id required: true schema: type: string format: uuid responses: '200': content: application/json: schema: $ref: '#/components/schemas/SecurityRemediationStartResult' description: Successful response '403': content: application/json: schema: $ref: '#/components/schemas/SecurityPermissionDenied' description: Permission or CSRF denied '404': content: application/json: schema: $ref: '#/components/schemas/SecurityDetailError' description: Organization-scoped resource not found '409': content: application/json: schema: $ref: '#/components/schemas/SecurityDetailError' description: >- Nothing to rebuild, the lane is unavailable, or every repository was refused '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Request validation error '500': content: application/json: schema: $ref: '#/components/schemas/SecurityDetailError' description: Internal server error security: - SessionCookie: [] servers: - url: https://api.platform.ankra.app components: schemas: SecurityRemediationStartResult: description: >- The runs a start answered, one per fix pull request (created false when the live run was reused), and the repositories the rebuild lane refused. properties: finding_id: type: string format: uuid refusals: items: $ref: '#/components/schemas/SecurityImageRebuildRefusal' type: array runs: items: properties: created: type: boolean run: $ref: '#/components/schemas/SecurityRemediationRun' required: - run - created type: object type: array required: - finding_id - runs - refusals type: object SecurityPermissionDenied: properties: detail: enum: - permission_denied type: string permission: type: string scope_type: type: string required: - detail - permission - scope_type type: object SecurityDetailError: properties: detail: type: string required: - detail type: object HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object SecurityImageRebuildRefusal: description: >- One image (repository, without tag) the lane cannot open a pull request for, and why. application_id, application_name and repository are null when no application could be attributed to the image. properties: application_id: format: uuid nullable: true type: string application_name: nullable: true type: string image_repository: type: string occurrences: type: integer reason: type: string repository: nullable: true type: string required: - application_id - application_name - repository - image_repository - occurrences - reason type: object SecurityRemediationRun: description: >- One remediation case for one fix pull request on one application (a finding's image rebuild, a base-image fix or a dependency bump): its fix pull request, the pipeline runs of its exact commits, and the rescan-based verification. verified needs a rescan of every affected cluster after the fix with no active occurrence; uncertain is a deadline passing without proof and never reads as clean. properties: finding_ids: description: Every finding the pull request fixes; what verification reads. items: type: string type: array findings: items: $ref: '#/components/schemas/SecurityFixedFinding' type: array kind: enum: - image_rebuild - base_image_proposal - dependency_bump type: string proposal_key: description: >- The fix's identity inside its application: finding: for a finding's rebuild, the pull request's branch for an application-batched fix. nullable: true type: string started_by: enum: - person - ankra type: string title: type: string trigger: description: What made Ankra start the run; null for a person's. nullable: true type: string application_id: type: string format: uuid application_name: type: string attempts: type: integer branch: type: string cluster_ids: type: array items: type: string created_at: type: string format: date-time deadline_at: type: string format: date-time failed_head_shas: type: array items: type: string finding_id: description: >- The one finding a per-finding fix is for; null for an application-batched fix. format: uuid nullable: true type: string id: type: string format: uuid image_repositories: type: array items: type: string last_head_sha: nullable: true type: string last_outcome: nullable: true type: string last_pipeline_run_id: format: uuid nullable: true type: string max_attempts: type: integer organisation_id: type: string format: uuid pipeline_concluded_at: format: date-time nullable: true type: string pipeline_repository_id: format: uuid nullable: true type: string pull_request_number: nullable: true type: integer pull_request_url: type: string repository: type: string requested_by: format: uuid nullable: true type: string status: enum: - working - verifying - verified - needs_human - uncertain - failed - cancelled type: string status_reason: type: string updated_at: type: string format: date-time verified_at: format: date-time nullable: true type: string verified_head_sha: nullable: true type: string required: - finding_ids - findings - kind - proposal_key - started_by - title - trigger - application_id - application_name - attempts - branch - cluster_ids - created_at - deadline_at - failed_head_shas - finding_id - id - image_repositories - last_head_sha - last_outcome - last_pipeline_run_id - max_attempts - organisation_id - pipeline_concluded_at - pipeline_repository_id - pull_request_number - pull_request_url - repository - requested_by - status - status_reason - updated_at - verified_at - verified_head_sha 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 SecurityFixedFinding: description: >- One finding a fix pull request fixes, as it stood when the run started: the vulnerability, the package and the version the fix moves it from and to. properties: from: type: string id: type: string format: uuid package: type: string severity: type: string to: type: string vulnerability_id: type: string required: - from - id - package - severity - to - vulnerability_id type: object securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http SessionCookie: description: Browser session. Mutations also require X-Ankra-CSRF. in: cookie name: ankra_session type: apiKey ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.