Confluent · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Confluent Cloud IP Filters (iam/v2) API

6 actions 6 updates phrasing extends openapi/confluent-ip-filters-iam-v2-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Confluent's API. It is a proposal applied on top of the contract, not a document Confluent publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 6

$.info
$.paths['/iam/v2/ip-filters'].get
$.paths['/iam/v2/ip-filters'].post
$.paths['/iam/v2/ip-filters/{id}'].get
$.paths['/iam/v2/ip-filters/{id}'].delete
$.paths['/iam/v2/ip-filters/{id}'].patch

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 Confluent Cloud IP Filters (iam/v2) API
  version: 1.0.0
extends: openapi/confluent-ip-filters-iam-v2-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: 5
- target: $.paths['/iam/v2/ip-filters'].get
  update:
    x-apievangelist-phrasing:
      intent: List IP filters
      effect: read
      questions:
      - Which IP filters restrict access to my Confluent Cloud organization?
      - Can I include filters inherited from parent scopes when listing?
      instructions:
      - text: List all IP filters.
      - text: List IP filters for scope {resource_scope}, including parent scopes {include_parent_scopes}.
        slots:
          resource_scope: query.resource_scope
          include_parent_scopes: query.include_parent_scopes
      method: generated
      generated: '2026-09-26'
- target: $.paths['/iam/v2/ip-filters'].post
  update:
    x-apievangelist-phrasing:
      intent: Create an IP filter
      effect: write
      questions:
      - How do I allow access only from my corporate IP ranges?
      - Can I apply an IP filter to specific operation groups like management or schema?
      instructions:
      - text: Create IP filter {filter_name} allowing IP groups {ip_groups}.
        slots:
          filter_name: requestBody.filter_name
          ip_groups: requestBody.ip_groups
      - text: Create IP filter {filter_name} for operation groups {operation_groups} on scope {resource_scope}.
        slots:
          filter_name: requestBody.filter_name
          operation_groups: requestBody.operation_groups
          resource_scope: requestBody.resource_scope
      method: generated
      generated: '2026-09-26'
- target: $.paths['/iam/v2/ip-filters/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get one IP filter
      effect: read
      questions:
      - Which IP groups and operations does a particular IP filter cover?
      - What does one IP filter look like when read by ID?
      instructions:
      - text: Get IP filter {id}.
        slots:
          id: path.id
      - text: Show the IP groups on filter {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/iam/v2/ip-filters/{id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete an IP filter
      effect: destructive
      questions:
      - How do I remove an IP filter that is blocking legitimate traffic?
      - Does deleting an IP filter reopen access from all addresses?
      instructions:
      - text: Delete IP filter {id}.
        slots:
          id: path.id
      - text: Remove the IP allowlist filter {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/iam/v2/ip-filters/{id}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update an IP filter
      effect: write
      questions:
      - Can I add another IP group to an existing filter?
      - How do I rename an IP filter or change its operation groups?
      instructions:
      - text: Update IP filter {id} to use IP groups {ip_groups}.
        slots:
          id: path.id
          ip_groups: requestBody.ip_groups
      - text: Rename IP filter {id} to {filter_name}.
        slots:
          id: path.id
          filter_name: requestBody.filter_name
      method: generated
      generated: '2026-09-26'