Act! CRM · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for act.web.api Cors API

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

What the actions change

x-apievangelist-phrasing

Targets 5

$.info
$.paths['/api/Cors'].get
$.paths['/api/Cors/{id}'].get
$.paths['/api/Cors/{id}'].put
$.paths['/api/Cors/{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 act.web.api Cors API
  version: 1.0.0
extends: openapi/act-cors-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: 4
- target: $.paths['/api/Cors'].get
  update:
    x-apievangelist-phrasing:
      intent: List allowed CORS origins
      effect: read
      questions:
      - Which web origins are allowed to call my Act! API from a browser?
      - What CORS domains are configured right now?
      instructions:
      - text: List all allowed CORS origins.
      - text: Show every domain in the CORS allow list.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/Cors/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Check one CORS origin entry
      effect: read
      questions:
      - Is a particular domain on the CORS allow list?
      - How do I look up a single CORS entry?
      instructions:
      - text: Check whether {id} is an allowed CORS origin.
        slots:
          id: path.id
      - text: Fetch the CORS entry {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/Cors/{id}'].put
  update:
    x-apievangelist-phrasing:
      intent: Allow a new CORS origin
      effect: write
      questions:
      - How do I let my web app's domain call the API cross-origin?
      - Can I add a domain with a port to the CORS config?
      instructions:
      - text: Add {id} to the allowed CORS origins.
        slots:
          id: path.id
      - text: Allow cross-origin requests from {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/Cors/{id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Remove a CORS origin
      effect: destructive
      questions:
      - How do I stop a domain from calling the API from the browser?
      - Can I take an origin off the CORS allow list?
      instructions:
      - text: Remove {id} from the allowed CORS origins.
        slots:
          id: path.id
      - text: Block cross-origin requests from {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-10-01'