> ## 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. # Replace repository workspace profiles > Bearer PAT authentication; RBAC permission `workspaces.manage`. Replaces the repository's workspace profiles; `null` or `{}` clears them. Every profile is validated as a workspace would be rendered from it. A running workspace picks the change up at its owner's next bring-up, which replaces it. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json put /api/v1/org/pipeline-repositories/{repository_id}/workspace-profiles 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: /api/v1/org/pipeline-repositories/{repository_id}/workspace-profiles: put: tags: - Workspaces summary: Replace repository workspace profiles description: >- Bearer PAT authentication; RBAC permission `workspaces.manage`. Replaces the repository's workspace profiles; `null` or `{}` clears them. Every profile is validated as a workspace would be rendered from it. A running workspace picks the change up at its owner's next bring-up, which replaces it. operationId: put_repository_workspace_profiles_pat parameters: - description: PAT organisation override. in: header name: x-ankra-organisation-id required: false schema: type: string - description: The connected pipeline repository. in: path name: repository_id required: true schema: type: string format: uuid requestBody: content: application/json: schema: $ref: '#/components/schemas/RepositoryWorkspaceProfilesUpdateRequest' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/RepositoryWorkspaceProfiles' description: Successful response '400': content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' description: A profile a workspace could not be rendered from '401': content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' description: Unauthenticated '403': content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' description: Permission check failed '404': content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' description: The repository is not connected in this organisation '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Request validation failed '500': content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' description: Internal failure security: - BearerAuth: [] components: schemas: RepositoryWorkspaceProfilesUpdateRequest: properties: profiles: additionalProperties: $ref: '#/components/schemas/WorkspaceProfile' description: The profiles keyed by kind; `null` or `{}` clears them. type: - object - 'null' required: - profiles title: RepositoryWorkspaceProfilesUpdateRequest type: object RepositoryWorkspaceProfiles: properties: profiles: additionalProperties: $ref: '#/components/schemas/WorkspaceProfile' type: object repository_id: type: string format: uuid required: - repository_id - profiles title: RepositoryWorkspaceProfiles type: object ContractDetailError: example: detail: Cluster not found properties: detail: oneOf: - type: string - additionalProperties: true properties: {} type: object required: - detail type: object HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object WorkspaceProfile: description: >- What a repository's workspace of one kind runs. Every field is optional: an empty image falls back to the repository's pipeline, an empty size to 2 CPU, 4Gi and a 20Gi volume. Tools are pinned downloads installed on the main container's PATH before it starts; setup is commands run once per workspace before its first command. properties: image: type: string resources: properties: cpu: type: string memory: description: >- The main container's memory, both its request and its limit, as a Kubernetes quantity (default 4Gi). A command that goes past it is OOMKilled, which restarts the container and ends every run in it; such a run carries an `error_message` saying so. type: string type: object services: description: >- Sidecars the workspace runs beside the main container, reached at their name as hostname. Every service runs as uid and gid 65534 (nobody), not as the user its image names, so a service that writes its data to a directory its image's own user owns needs pointing at a writable one: postgres, for example, needs `PGDATA` set to a directory such as `/tmp/pgdata`. items: properties: env: type: object additionalProperties: type: string image: type: string name: type: string ports: items: type: - string - integer type: array ready: properties: http: type: string tcp: type: string type: object required: - name - image type: object type: array setup: description: >- Shell commands run once per workspace, in order, in the run's worktree before its command starts; run again when they or the tools change. A failing one ends the run not started with exit code 78. At most 16, each one line of at most 2048 bytes. items: type: string maxItems: 16 type: array tools: description: >- Pinned downloads installed before the main container starts and put first on the PATH of every command a run starts. A download whose SHA-256 differs from the pin is refused and fails the workspace. Tool URLs are not held to the organisation's image policy: https and the pinned sha256 are what holds them. items: properties: bin: description: >- For a .tar.gz or .tgz download, the executable's path inside the archive after strip_components; defaults to name. type: string name: description: The command the tool is run as. type: string sha256: description: The download's SHA-256, 64 lower-case hex digits. type: string strip_components: description: >- For a .tar.gz or .tgz download, how many leading directories are dropped when it is extracted. type: integer url: description: >- An https:// URL. A path ending in .tar.gz or .tgz is an archive; anything else is the executable itself. type: string required: - name - url - sha256 type: object maxItems: 16 type: array volume_size: type: string title: WorkspaceProfile 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 securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.