Elation Health · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Elation Health Recurring Event Groups API

10 actions 10 updates phrasing extends openapi/elation-health-recurring-event-groups-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Elation Health's API. It is a proposal applied on top of the contract, not a document Elation Health publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 10

$.info
$.paths['/recurring_event_groups/{id}/'].get
$.paths['/recurring_event_groups/{id}/'].delete
$.paths['/recurring_event_groups/'].get
$.paths['/recurring_event_groups/'].post
$.paths['/recurring_event_groups/:id/'].put
$.paths['/api/2.0/recurring_event_groups/'].get
$.paths['/api/2.0/recurring_event_groups/'].post
$.paths['/api/2.0/recurring_event_groups/{id}/'].get
$.paths['/api/2.0/recurring_event_groups/{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 Elation Health Recurring Event Groups API
  version: 1.0.0
extends: openapi/elation-health-recurring-event-groups-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: 9
- target: $.paths['/recurring_event_groups/{id}/'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a recurring event group (legacy)
      effect: read
      questions:
      - How do I see the details of one recurring calendar block on the older endpoint?
      - Which legacy call returns a recurring event group by ID?
      instructions:
      - text: Get legacy recurring event group {id}.
        slots:
          id: path.id
      - text: Show the schedule of older recurring block {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/recurring_event_groups/{id}/'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a recurring event group (legacy)
      effect: destructive
      questions:
      - How do I remove a repeating calendar block with the older delete call?
      - Which unversioned endpoint deletes a recurring event group?
      instructions:
      - text: Delete legacy recurring event group {id}.
        slots:
          id: path.id
      - text: Remove old repeating calendar block {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/recurring_event_groups/'].get
  update:
    x-apievangelist-phrasing:
      intent: Find recurring event groups (legacy)
      effect: read
      questions:
      - Which recurring blocks are on a physician's calendar, per the older endpoint?
      - Can I find legacy recurring events by reason within a date range?
      instructions:
      - text: Find legacy recurring event groups for physician {physician}.
        slots:
          physician: query.physician
      - text: Search older recurring blocks with reason {reason} between {start_date} and {end_date}.
        slots:
          reason: query.reason
          start_date: query.start_date
          end_date: query.end_date
      method: generated
      generated: '2026-09-26'
- target: $.paths['/recurring_event_groups/'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a recurring event group (legacy)
      effect: write
      questions:
      - Is there an older unversioned route for adding a repeating calendar block?
      - Which legacy call creates recurring events?
      instructions:
      - text: Create a recurring event group through the legacy route.
      - text: Add an older-style repeating calendar block.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/recurring_event_groups/:id/'].put
  update:
    x-apievangelist-phrasing:
      intent: Update a recurring event group (legacy)
      effect: write
      questions:
      - Is there an older colon-path route for editing a repeating calendar block?
      - Which legacy call changes a recurring event group?
      instructions:
      - text: Update a recurring event group through the legacy colon-style path.
      - text: Edit an older-style repeating calendar block.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/recurring_event_groups/'].get
  update:
    x-apievangelist-phrasing:
      intent: List recurring event groups with filters
      effect: read
      questions:
      - How do I page through recurring calendar blocks in the v2.0 API?
      - Can I filter v2.0 recurring events by time slot type?
      instructions:
      - text: List v2.0 recurring event groups of time slot type {time_slot_type} for practice {practice}.
        slots:
          time_slot_type: query.time_slot_type
          practice: query.practice
      - text: Page through /api/2.0 recurring blocks from {start_date} to {end_date}, {limit} per page.
        slots:
          start_date: query.start_date
          end_date: query.end_date
          limit: query.limit
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/recurring_event_groups/'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a recurring event group in v2.0
      effect: write
      questions:
      - How do I block off a repeating time slot on the calendar through /api/2.0?
      - Can a v2.0 recurring event block appointments from being booked?
      instructions:
      - text: Create a v2.0 recurring event group for practice {practice} with schedules {schedules} and time slot type {time_slot_type}.
        slots:
          practice: requestBody.practice
          schedules: requestBody.schedules
          time_slot_type: requestBody.time_slot_type
      - text: Add an /api/2.0 repeating block for reason {reason} that is blocking {is_blocking}.
        slots:
          reason: requestBody.reason
          is_blocking: requestBody.is_blocking
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/recurring_event_groups/{id}/'].get
  update:
    x-apievangelist-phrasing:
      intent: Retrieve a recurring event group from v2.0
      effect: read
      questions:
      - How do I fetch one recurring event group by ID from /api/2.0?
      - Does a v2.0 recurring block show whether it is blocking?
      instructions:
      - text: Retrieve v2.0 recurring event group {id}.
        slots:
          id: path.id
      - text: Show the schedules on /api/2.0 recurring block {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/recurring_event_groups/{id}/'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a recurring event group in v2.0
      effect: destructive
      questions:
      - How do I delete a recurring calendar block through /api/2.0?
      - Can I cancel a v2.0 repeating time slot series?
      instructions:
      - text: Delete v2.0 recurring event group {id}.
        slots:
          id: path.id
      - text: Cancel the /api/2.0 repeating series {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/elation-health-recurring-event-groups-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.