# 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 Office Staff API
  version: 1.0.0
extends: openapi/elation-health-office-staff-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: 6
- target: $.paths['/office_staff/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get an office staff member (legacy)
      effect: read
      questions:
      - Can I look up one office staff member on the legacy path?
      - What contact details does the original endpoint return for a staff member?
      instructions:
      - text: Get legacy office staff member {id}.
        slots:
          id: path.id
      - text: Show staff member {id} from the older endpoint.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/office_staff/{id}'].put
  update:
    x-apievangelist-phrasing:
      intent: Update an office staff member
      effect: write
      questions:
      - Can I change a staff member's email or phone?
      - How do I correct an office staff member's name?
      instructions:
      - text: Update office staff {id} with email {email}.
        slots:
          id: path.id
          email: requestBody.email
      - text: Change staff member {id}'s last name to {last}.
        slots:
          id: path.id
          last: requestBody.last_name
      method: generated
      generated: '2026-09-26'
- target: $.paths['/office_staff/'].get
  update:
    x-apievangelist-phrasing:
      intent: List office staff (legacy endpoint)
      effect: read
      questions:
      - Who is on my practice's office staff, per the legacy endpoint?
      - Can I see all non-clinical staff accounts on the original path?
      instructions:
      - text: List office staff from the legacy endpoint.
      - text: Show every office staff member on the old path.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/office_staff/'].post
  update:
    x-apievangelist-phrasing:
      intent: Add an office staff member
      effect: write
      questions:
      - How do I add a new front-desk staff member to my practice?
      - What details can I record when creating an office staff member?
      instructions:
      - text: Create office staff member {first} {last} in practice {practice}.
        slots:
          first: requestBody.first_name
          last: requestBody.last_name
          practice: requestBody.practice
      - text: Add staff member {first} {last} with email {email}.
        slots:
          first: requestBody.first_name
          last: requestBody.last_name
          email: requestBody.email
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/office_staff/'].get
  update:
    x-apievangelist-phrasing:
      intent: List office staff (v2.0)
      effect: read
      questions:
      - Is it possible to page through office staff in the 2.0 API?
      - Can I sort version 2.0 office staff?
      instructions:
      - text: List v2.0 office staff.
      - text: List 2.0 office staff ordered by {order_by}.
        slots:
          order_by: query.order_by
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/office_staff/{staff_id}/'].get
  update:
    x-apievangelist-phrasing:
      intent: Get an office staff member (v2.0)
      effect: read
      questions:
      - Can I fetch one staff member by staff id in the 2.0 API?
      - Which v2.0 call returns a single office staff record by staff id?
      instructions:
      - text: Get v2.0 office staff member {staff}.
        slots:
          staff: path.staff_id
      - text: Retrieve staff {staff} from the 2.0 API.
        slots:
          staff: path.staff_id
      method: generated
      generated: '2026-09-26'