# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Multi-Location Analytics Analytics Service API
  version: 1.0.0
extends: openapi/vendasta-analyticsservice-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: 2
- target: $.paths['/v1/multi-location-analytics/available-metrics'].post
  update:
    x-apievangelist-phrasing:
      intent: Discover available analytics metrics
      effect: read
      questions:
      - Which analytics metrics, measures and dimensions can I query for a business?
      - Why do I get InvalidArgument when mixing business and market resources in the metric catalog?
      instructions:
      - text: List the metrics available to partner {partnerId} for resources {resourceIds}.
        slots:
          partnerId: requestBody.partnerId
          resourceIds: requestBody.resourceIds
      - text: Show the metric catalog for business {resourceIds} under partner {partnerId}.
        slots:
          resourceIds: requestBody.resourceIds
          partnerId: requestBody.partnerId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v1/multi-location-analytics/query'].post
  update:
    x-apievangelist-phrasing:
      intent: Query multi-location analytics metrics
      effect: read
      questions:
      - What are the top 10 businesses by review count this quarter?
      - Can I group and filter a metric across multiple locations over a time range?
      instructions:
      - text: Query metric {metricName} for partner {partnerId} across resources {resourceIds}.
        slots:
          metricName: requestBody.metricName
          partnerId: requestBody.partnerId
          resourceIds: requestBody.resourceIds
      - text: Get the top {limit} of {resourceIds} by {metricName} for partner {partnerId}, ordered by {orderBy}.
        slots:
          limit: requestBody.limit
          resourceIds: requestBody.resourceIds
          metricName: requestBody.metricName
          partnerId: requestBody.partnerId
          orderBy: requestBody.orderBy
      method: generated
      generated: '2026-10-01'