Loops · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Loops OpenAPI Spec Components API

5 actions 5 updates phrasing extends openapi/loops-components-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Loops's API. It is a proposal applied on top of the contract, not a document Loops publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 5

$.info
$.paths['/v1/components/{componentId}'].get
$.paths['/v1/components/{componentId}'].post
$.paths['/v1/components'].get
$.paths['/v1/components'].post

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 Loops OpenAPI Spec Components API
  version: 1.0.0
extends: openapi/loops-components-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: 4
- target: $.paths['/v1/components/{componentId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get an email component
      effect: read
      questions:
      - How do I view the LMX body of a reusable email component?
      - What does a specific component contain?
      instructions:
      - text: Show email component {componentId}.
        slots:
          componentId: path.componentId
      - text: Get the LMX for component {componentId}.
        slots:
          componentId: path.componentId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/components/{componentId}'].post
  update:
    x-apievangelist-phrasing:
      intent: Update an email component
      effect: write
      questions:
      - If I edit a shared component, do the emails using it change too?
      - How do I change the body of an existing component?
      instructions:
      - text: Replace the LMX of component {componentId} with {lmx}.
        slots:
          componentId: path.componentId
          lmx: requestBody.lmx
      - text: Rename component {componentId} to {name}.
        slots:
          componentId: path.componentId
          name: requestBody.name
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/components'].get
  update:
    x-apievangelist-phrasing:
      intent: List email components
      effect: read
      questions:
      - Which reusable email components exist on my team?
      - Can I page through all components?
      instructions:
      - text: List my email components.
      - text: Show {perPage} components per page.
        slots:
          perPage: query.perPage
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/components'].post
  update:
    x-apievangelist-phrasing:
      intent: Create an email component
      effect: write
      questions:
      - How do I create a reusable block I can drop into emails?
      - What format does a new component body need to be in?
      instructions:
      - text: Create a component named {name} from LMX {lmx}.
        slots:
          name: requestBody.name
          lmx: requestBody.lmx
      - text: Save this LMX {lmx} as a new component called {name}.
        slots:
          lmx: requestBody.lmx
          name: requestBody.name
      method: generated
      generated: '2026-09-26'