# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Azure API Management REST API Version Set API
  version: 1.0.0
extends: openapi/microsoft-azure-api-management-apiversionset-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 5
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/workspaces/{workspaceId}/apiVersionSets'].get
  update:
    x-apievangelist-phrasing:
      intent: List API version sets in a workspace
      effect: read
      questions:
      - Which API version sets are defined in one of my workspaces?
      - Can I see how the APIs in a workspace are grouped into versions?
      instructions:
      - text: List every API version set in workspace {workspaceId} on service {serviceName}.
        slots:
          workspaceId: path.workspaceId
          serviceName: path.serviceName
      - text: Show me the workspace's version sets.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/workspaces/{workspaceId}/apiVersionSets/{versionSetId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get an API version set
      effect: read
      questions:
      - How do I see the versioning scheme of one version set?
      - Does a particular version set use a header, query string or path segment?
      instructions:
      - text: Get version set {versionSetId} from workspace {workspaceId} on service {serviceName}.
        slots:
          versionSetId: path.versionSetId
          workspaceId: path.workspaceId
          serviceName: path.serviceName
      - text: Show me the versioning scheme of one workspace version set.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/workspaces/{workspaceId}/apiVersionSets/{versionSetId}'].put
  update:
    x-apievangelist-phrasing:
      intent: Create or replace an API version set
      effect: write
      questions:
      - How do I set up a version set so my API can have multiple versions in API Management?
      - Can I overwrite an existing workspace version set in one call?
      instructions:
      - text: Create version set {versionSetId} in workspace {workspaceId} on service {serviceName}.
        slots:
          versionSetId: path.versionSetId
          workspaceId: path.workspaceId
          serviceName: path.serviceName
      - text: Create or fully replace this workspace API version set.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/workspaces/{workspaceId}/apiVersionSets/{versionSetId}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update an API version set
      effect: write
      questions:
      - Can I change a version set's name or scheme without recreating it?
      - Is there a way to patch an existing workspace version set?
      instructions:
      - text: Patch the existing version set {versionSetId} in workspace {workspaceId} on service {serviceName}.
        slots:
          versionSetId: path.versionSetId
          workspaceId: path.workspaceId
          serviceName: path.serviceName
      - text: Rename a workspace API version set that already exists.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/workspaces/{workspaceId}/apiVersionSets/{versionSetId}'].head
  update:
    x-apievangelist-phrasing:
      intent: Get an API version set's ETag
      effect: read
      questions:
      - Can I read a version set's ETag before editing it?
      - Does a version set with a given ID exist in my workspace?
      instructions:
      - text: Check the ETag of version set {versionSetId} in workspace {workspaceId} on service {serviceName}.
        slots:
          versionSetId: path.versionSetId
          workspaceId: path.workspaceId
          serviceName: path.serviceName
      - text: Confirm this workspace version set exists from its entity state header.
      method: generated
      generated: '2026-10-01'