Infobip · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Infobip OpenAPI Specification Tools API

4 actions 4 updates phrasing extends openapi/infobip-tools-api-openapi.yml

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

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 4

$.info

$.paths['/platform/1/openapi'].get

$.paths['/platform/1/openapi/{product}'].get

$.paths['/platform/1/openapi/available-products'].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 Infobip OpenAPI Specification Tools API
  version: 1.0.0
extends: openapi/infobip-tools-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['/platform/1/openapi'].get
  update:
    x-apievangelist-phrasing:
      intent: Download the full platform OpenAPI specification
      effect: read
      questions:
      - Where can I download the complete OpenAPI spec covering every Infobip endpoint and webhook?
      - Is there one OpenAPI document for the whole platform rather than per channel?
      instructions:
      - text: Fetch the complete OpenAPI specification for the entire platform.
      - text: Download the all-products OpenAPI document so I can generate a client for every endpoint.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/platform/1/openapi/{product}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get the OpenAPI specification for one product
      effect: read
      questions:
      - How do I get just the SMS OpenAPI spec instead of the whole platform document?
      - Can I pull an OpenAPI definition scoped to a single product like Email or WhatsApp?
      instructions:
      - text: Get the OpenAPI specification for the {product} product.
        slots:
          product: path.product
      - text: Download only the {product} product's OpenAPI definition.
        slots:
          product: path.product
      method: generated
      generated: '2026-09-26'
- target: $.paths['/platform/1/openapi/available-products'].get
  update:
    x-apievangelist-phrasing:
      intent: List products that have their own OpenAPI spec
      effect: read
      questions:
      - Which product identifiers can I use when fetching a per-product OpenAPI spec?
      - What products are available to download a separate specification for?
      instructions:
      - text: List the available products and their identifiers for per-product specs.
      - text: Show me which product names I can pass to get a product-level OpenAPI document.
      method: generated
      generated: '2026-09-26'