# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Elation Health Service Locations API
  version: 1.0.0
extends: openapi/elation-health-service-locations-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: 12
- target: $.paths['/service_locations'].get
  update:
    x-apievangelist-phrasing:
      intent: List service locations (legacy endpoint)
      effect: read
      questions:
      - What service locations does my practice have, per the legacy endpoint?
      - Can I see all practice addresses from the original service locations path?
      instructions:
      - text: List my service locations from the legacy endpoint.
      - text: Show every practice address on the old service locations path.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/service_locations'].post
  update:
    x-apievangelist-phrasing:
      intent: Add a service location (legacy endpoint)
      effect: write
      questions:
      - How do I add a new office location for my practice through the legacy endpoint?
      - Can I flag a new service location as primary using the original path?
      instructions:
      - text: Create legacy service location {name} at {address}, {city}, {state} for practice {practice}.
        slots:
          name: requestBody.name
          address: requestBody.address_line1
          city: requestBody.city
          state: requestBody.state
          practice: requestBody.practice
      - text: Add an old-endpoint location {name} in {city}, {state} with phone {phone}.
        slots:
          name: requestBody.name
          city: requestBody.city
          state: requestBody.state
          phone: requestBody.phone
      method: generated
      generated: '2026-09-26'
- target: $.paths['/service_locations/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a service location (legacy endpoint)
      effect: read
      questions:
      - How do I look up one service location by id on the legacy path?
      - What address and place of service does the original endpoint return for a location?
      instructions:
      - text: Get legacy service location {id}.
        slots:
          id: path.id
      - text: Show location {id} from the older service locations endpoint.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/service_locations/{id}'].put
  update:
    x-apievangelist-phrasing:
      intent: Replace a service location (legacy PUT)
      effect: write
      questions:
      - Can I overwrite a whole service location with the legacy PUT?
      - Which legacy call requires resending the full address of a location?
      instructions:
      - text: Replace legacy service location {id} with address {address}, {city}, {state}.
        slots:
          id: path.id
          address: requestBody.address_line1
          city: requestBody.city
          state: requestBody.state
      - text: Overwrite old-endpoint location {id} in full, naming it {name}.
        slots:
          id: path.id
          name: requestBody.name
      method: generated
      generated: '2026-09-26'
- target: $.paths['/service_locations/{id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a service location (legacy endpoint)
      effect: destructive
      questions:
      - How do I remove a closed office location using the legacy endpoint?
      - Can I delete a service location through the original path?
      instructions:
      - text: Delete legacy service location {id}.
        slots:
          id: path.id
      - text: Remove location {id} via the old endpoint.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/service_locations/{id}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Change a service location's contact info (legacy)
      effect: write
      questions:
      - Can I update just the phone or fax of a location with the legacy PATCH?
      - How do I make a different location primary on the unversioned path?
      instructions:
      - text: Patch legacy location {id} with phone {phone} and fax {fax}.
        slots:
          id: path.id
          phone: requestBody.phone
          fax: requestBody.fax
      - text: Set old-endpoint location {id} as primary {primary}.
        slots:
          id: path.id
          primary: requestBody.is_primary
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/service_locations/'].get
  update:
    x-apievangelist-phrasing:
      intent: List service locations (v2.0)
      effect: read
      questions:
      - How do I page through service locations in the 2.0 API?
      - Can I sort version 2.0 service locations?
      instructions:
      - text: List v2.0 service locations.
      - text: List 2.0 service locations ordered by {order_by}, {limit} per page.
        slots:
          order_by: query.order_by
          limit: query.limit
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/service_locations/'].post
  update:
    x-apievangelist-phrasing:
      intent: Add a service location (v2.0)
      effect: write
      questions:
      - How do I create a service location with a timezone in version 2.0?
      - Which fields are required for a new location in the 2.0 API?
      instructions:
      - text: Create v2.0 service location {name} at {address} in {state} for practice {practice}.
        slots:
          name: requestBody.name
          address: requestBody.address_line1
          state: requestBody.state
          practice: requestBody.practice
      - text: Add 2.0 location {name} with place of service code {pos} and timezone {tz}.
        slots:
          name: requestBody.name
          pos: requestBody.place_of_service_code
          tz: requestBody.timezone
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/service_locations/{id}/'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a service location (v2.0)
      effect: read
      questions:
      - How do I fetch one service location in the 2.0 API?
      - Does the v2.0 location record include its timezone and status?
      instructions:
      - text: Get v2.0 service location {id}.
        slots:
          id: path.id
      - text: Retrieve location {id} from the 2.0 API.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/service_locations/{id}/'].put
  update:
    x-apievangelist-phrasing:
      intent: Replace a service location (v2.0 PUT)
      effect: write
      questions:
      - Can I fully replace a service location in version 2.0?
      - Which 2.0 call overwrites every service location field?
      instructions:
      - text: Replace v2.0 service location {id} named {name} at {address}, {state}.
        slots:
          id: path.id
          name: requestBody.name
          address: requestBody.address_line1
          state: requestBody.state
      - text: Overwrite 2.0 location {id} for practice {practice}.
        slots:
          id: path.id
          practice: requestBody.practice
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/service_locations/{id}/'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a service location (v2.0)
      effect: destructive
      questions:
      - How do I delete a service location through the 2.0 API?
      - Can I remove an office we closed in version 2.0?
      instructions:
      - text: Delete v2.0 service location {id}.
        slots:
          id: path.id
      - text: Remove location {id} using the 2.0 endpoint.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/service_locations/{id}/'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update some service location fields (v2.0)
      effect: write
      questions:
      - Can I change only a location's timezone in the 2.0 API?
      - Which v2.0 call updates a location's email without resending the address?
      instructions:
      - text: Patch v2.0 location {id} timezone to {tz}.
        slots:
          id: path.id
          tz: requestBody.timezone
      - text: Update the email on 2.0 service location {id} to {email}.
        slots:
          id: path.id
          email: requestBody.email
      method: generated
      generated: '2026-09-26'