Toast · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Analytics Guest API

3 actions 3 updates phrasing extends openapi/toast-guest-api-openapi.yml

Generated by API Evangelist Written by API Evangelist tooling for Toast's API. It is a proposal applied on top of the contract, not a document Toast publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info

$.paths['/guest/payments/{timeRange}'].post

$.paths['/guest/payments/{reportRequestGuid}'].get

OpenAPI Overlay

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Analytics Guest API
  version: 1.0.0
extends: openapi/toast-guest-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['/guest/payments/{timeRange}'].post
  update:
    x-apievangelist-phrasing:
      intent: Request guest data organized by payment
      effect: write
      questions:
      - How do I request a report of guest data organized by payment for a date range?
      - Can I limit a guest-by-payment report to inactive restaurants?
      instructions:
      - text: Request {time_range} guest data by payment from {start} to {end} for {restaurants}.
        slots:
          time_range: path.timeRange
          start: requestBody.startDate
          end: requestBody.endDate
          restaurants: requestBody.restaurantIds
      - text: Start a guest-by-payment report from {start} to {end} excluding {excluded}.
        slots:
          start: requestBody.startDate
          end: requestBody.endDate
          excluded: requestBody.excludedRestaurantIds
      method: generated
      generated: '2026-10-01'
- target: $.paths['/guest/payments/{reportRequestGuid}'].get
  update:
    x-apievangelist-phrasing:
      intent: Fetch guest-by-payment report results
      effect: read
      questions:
      - Where do I collect the guest data once my guest-by-payment request is done?
      - What does the guest reporting data organized by payment return?
      instructions:
      - text: Get guest-by-payment results for report request {report}.
        slots:
          report: path.reportRequestGuid
      - text: Fetch the guest data by payment for request {report}.
        slots:
          report: path.reportRequestGuid
      method: generated
      generated: '2026-10-01'