Acronis · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Account Management Infra API

6 actions 6 updates phrasing extends openapi/acronis-infra-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Acronis's API. It is a proposal applied on top of the contract, not a document Acronis publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 6

$.info
$.paths['/infra'].get
$.paths['/infra'].post
$.paths['/infra/{infra_id}'].get
$.paths['/infra/{infra_id}'].put
$.paths['/infra/{infra_id}'].delete

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Account Management Infra API
  version: 1.0.0
extends: openapi/acronis-infra-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 5
- target: $.paths['/infra'].get
  update:
    x-apievangelist-phrasing:
      intent: Fetch several infrastructure components
      effect: read
      questions:
      - Can I get details of several infrastructure components by UUID at once?
      - How do I look up a batch of storage backends?
      instructions:
      - text: Fetch infrastructure components {uuids}.
        slots:
          uuids: query.uuids
      - text: Show infra components with UUIDs {uuids}.
        slots:
          uuids: query.uuids
      method: generated
      generated: '2026-09-26'
- target: $.paths['/infra'].post
  update:
    x-apievangelist-phrasing:
      intent: Register an infrastructure component
      effect: write
      questions:
      - How do I register a new storage infrastructure component?
      - What capabilities and URL does an infrastructure component need?
      instructions:
      - text: Register infrastructure {name} at {url} with capabilities {capabilities} for tenant {owner_tenant_id}.
        slots:
          name: requestBody.name
          url: requestBody.url
          capabilities: requestBody.capabilities
          owner_tenant_id: requestBody.owner_tenant_id
      - text: Add infrastructure component {name} in location {location_id}.
        slots:
          name: requestBody.name
          location_id: requestBody.location_id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/infra/{infra_id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get an infrastructure component
      effect: read
      questions:
      - What are the settings of this infrastructure component?
      - Can I see an infrastructure component's backend type and URL?
      instructions:
      - text: Show infrastructure component {infra_id}.
        slots:
          infra_id: path.infra_id
      - text: Get details of infra {infra_id}.
        slots:
          infra_id: path.infra_id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/infra/{infra_id}'].put
  update:
    x-apievangelist-phrasing:
      intent: Update an infrastructure component
      effect: write
      questions:
      - How do I change the URL or name of an infrastructure component?
      - Can I move an infrastructure component to another location?
      instructions:
      - text: Update infrastructure {infra_id} URL to {url} at version {version}.
        slots:
          infra_id: path.infra_id
          url: requestBody.url
          version: requestBody.version
      - text: Move infra {infra_id} to location {location_id}.
        slots:
          infra_id: path.infra_id
          location_id: requestBody.location_id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/infra/{infra_id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Unregister an infrastructure component
      effect: destructive
      questions:
      - How do I unregister an infrastructure component?
      - Can I unregister a component even if it still has usage?
      instructions:
      - text: Unregister infrastructure {infra_id} at version {version}.
        slots:
          infra_id: path.infra_id
          version: query.version
      - text: Force-unregister infra {infra_id}, ignoring existing usage.
        slots:
          infra_id: path.infra_id
      method: generated
      generated: '2026-09-26'