Twilio · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Twilio Accounts Auth Tokens API

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

What the actions change

x-apievangelist-phrasing

Targets 4

$.info
$.paths['/AuthTokens/Promote'].post
$.paths['/AuthTokens/Secondary'].post
$.paths['/AuthTokens/Secondary'].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 Twilio Accounts Auth Tokens API
  version: 1.0.0
extends: openapi/twilio-auth-tokens-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: 3
- target: $.paths['/AuthTokens/Promote'].post
  update:
    x-apievangelist-phrasing:
      intent: Promote the secondary auth token (legacy path)
      effect: destructive
      questions:
      - Can I promote my secondary auth token through the older unversioned endpoint?
      - Does the legacy promote call invalidate my old primary token immediately?
      instructions:
      - text: Promote my secondary auth token to primary using the legacy endpoint.
      - text: Call the unversioned /AuthTokens/Promote path to swap in the secondary token.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/AuthTokens/Secondary'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a secondary auth token (legacy path)
      effect: write
      questions:
      - Can I create a secondary auth token through the legacy unversioned endpoint?
      - Is the older secondary token endpoint still usable for zero-downtime rotation?
      instructions:
      - text: Create a secondary auth token via the legacy endpoint.
      - text: Generate a backup token using the unversioned /AuthTokens/Secondary path.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/AuthTokens/Secondary'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete the secondary auth token (legacy path)
      effect: destructive
      questions:
      - Can I delete my secondary auth token through the older unversioned path?
      - Is there a legacy call to discard a secondary token I created by mistake?
      instructions:
      - text: Delete my secondary auth token via the legacy endpoint.
      - text: Discard the backup token using the unversioned /AuthTokens/Secondary path.
      method: generated
      generated: '2026-09-26'