Cohesity · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Cohesity REST Connectors API

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

What the actions change

x-apievangelist-phrasing

Targets 11

$.info
$.paths['/connector-hybrid-extender'].get
$.paths['/connector-hybrid-extender'].post
$.paths['/connector-hybrid-extender/{id}'].get
$.paths['/connector-hybrid-extender/{id}'].put
$.paths['/connector-hybrid-extender/{id}'].delete
$.paths['/connector-rigel'].get
$.paths['/connector-rigel'].post
$.paths['/connector-rigel/{id}'].get
$.paths['/connector-rigel/{id}'].put
$.paths['/connector-rigel/{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 Cohesity REST Connectors API
  version: 1.0.0
extends: openapi/cohesity-connectors-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: 10
- target: $.paths['/connector-hybrid-extender'].get
  update:
    x-apievangelist-phrasing:
      intent: List Bifrost (hybrid extender) connectors
      effect: read
      questions:
      - Which Bifrost hybrid extender connectors are set up on the cluster?
      - Can I filter Bifrost connectors by tenant or connection?
      instructions:
      - text: List Bifrost connectors for tenant {tenantId}.
        slots:
          tenantId: query.tenantId
      - text: Find Bifrost connectors named {names}.
        slots:
          names: query.names
      method: generated
      generated: '2026-10-01'
- target: $.paths['/connector-hybrid-extender'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a Bifrost connector
      effect: write
      questions:
      - How do I add a Bifrost hybrid extender connector for a tenant?
      - What does a new Bifrost connector need, a connection and a tenant?
      instructions:
      - text: Create Bifrost connector {name} for tenant {tenantId} on connection {connectionId}.
        slots:
          name: requestBody.name
          tenantId: requestBody.tenantId
          connectionId: requestBody.connectionId
      - text: Add a hybrid extender connector {name} on connection {connectionId} for tenant {tenantId}.
        slots:
          name: requestBody.name
          connectionId: requestBody.connectionId
          tenantId: requestBody.tenantId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/connector-hybrid-extender/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a Bifrost connector
      effect: read
      questions:
      - What are the details of one Bifrost connector?
      - Can I look up a hybrid extender connector by its id?
      instructions:
      - text: Get Bifrost connector {id}.
        slots:
          id: path.id
      - text: Show Bifrost connector {id} for tenant {tenantId}.
        slots:
          id: path.id
          tenantId: query.tenantId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/connector-hybrid-extender/{id}'].put
  update:
    x-apievangelist-phrasing:
      intent: Update a Bifrost connector
      effect: write
      questions:
      - Can I rename a Bifrost connector or point it at another connection?
      - Which fields must be resent when updating a hybrid extender connector?
      instructions:
      - text: Rename Bifrost connector {id} to {name} for tenant {tenantId} on connection {connectionId}.
        slots:
          id: path.id
          name: requestBody.name
          tenantId: requestBody.tenantId
          connectionId: requestBody.connectionId
      - text: Move Bifrost connector {id} to connection {connectionId}, name {name}, tenant {tenantId}.
        slots:
          id: path.id
          connectionId: requestBody.connectionId
          name: requestBody.name
          tenantId: requestBody.tenantId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/connector-hybrid-extender/{id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a Bifrost connector
      effect: destructive
      questions:
      - Can I remove a Bifrost hybrid extender connector I no longer need?
      - What happens when a Bifrost connector is deleted?
      instructions:
      - text: Delete Bifrost connector {id}.
        slots:
          id: path.id
      - text: Remove hybrid extender connector {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-10-01'
- target: $.paths['/connector-rigel'].get
  update:
    x-apievangelist-phrasing:
      intent: List Rigel connectors
      effect: read
      questions:
      - Which Rigel connectors are configured on the cluster?
      - Can I filter Rigel connectors by name or tenant?
      instructions:
      - text: List Rigel connectors for tenant {tenantId}.
        slots:
          tenantId: query.tenantId
      - text: Find Rigel connectors named {names}.
        slots:
          names: query.names
      method: generated
      generated: '2026-10-01'
- target: $.paths['/connector-rigel'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a Rigel connector
      effect: write
      questions:
      - What do I need to create a Rigel connector, including its certificate version?
      - Can I register a Rigel connector for a tenant on a given connection?
      instructions:
      - text: Create Rigel connector {name} with id {connectorId}, cert version {certificateVersion}, tenant {tenantId}, connection {connectionId}.
        slots:
          name: requestBody.name
          connectorId: requestBody.connectorId
          certificateVersion: requestBody.certificateVersion
          tenantId: requestBody.tenantId
          connectionId: requestBody.connectionId
      - text: Register Rigel connector {connectorId} as {name} for tenant {tenantId} on {connectionId} using cert version {certificateVersion}.
        slots:
          connectorId: requestBody.connectorId
          name: requestBody.name
          tenantId: requestBody.tenantId
          connectionId: requestBody.connectionId
          certificateVersion: requestBody.certificateVersion
      method: generated
      generated: '2026-10-01'
- target: $.paths['/connector-rigel/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a Rigel connector
      effect: read
      questions:
      - What are the details of one Rigel connector?
      - Can I look up a Rigel connector by its id for a tenant?
      instructions:
      - text: Get Rigel connector {id}.
        slots:
          id: path.id
      - text: Show Rigel connector {id} for tenant {tenantId}.
        slots:
          id: path.id
          tenantId: query.tenantId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/connector-rigel/{id}'].put
  update:
    x-apievangelist-phrasing:
      intent: Update a Rigel connector
      effect: write
      questions:
      - Can I bump the certificate version of a Rigel connector?
      - Which fields must be resent when updating a Rigel connector?
      instructions:
      - text: Update Rigel connector {id} to cert version {certificateVersion}, name {name}, tenant {tenantId}, connection {connectionId}.
        slots:
          id: path.id
          certificateVersion: requestBody.certificateVersion
          name: requestBody.name
          tenantId: requestBody.tenantId
          connectionId: requestBody.connectionId
      - text: Rename Rigel connector {id} to {name} keeping tenant {tenantId}, connection {connectionId}, cert {certificateVersion}.
        slots:
          id: path.id
          name: requestBody.name
          tenantId: requestBody.tenantId
          connectionId: requestBody.connectionId
          certificateVersion: requestBody.certificateVersion
      method: generated
      generated: '2026-10-01'
- target: $.paths['/connector-rigel/{id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a Rigel connector
      effect: destructive
      questions:
      - Can I remove a Rigel connector that a tenant no longer uses?
      - Does deleting a Rigel connector require the tenant id?
      instructions:
      - text: Delete Rigel connector {id} for tenant {tenantId}.
        slots:
          id: path.id
          tenantId: requestBody.tenantId
      - text: Remove Rigel connector {id} from tenant {tenantId}.
        slots:
          id: path.id
          tenantId: requestBody.tenantId
      method: generated
      generated: '2026-10-01'

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay 
curl "https://apis.io/api/v1/overlays/cohesity-connectors-api-phrasing-overlay"
All openapi overlays 
curl "https://apis.io/api/v1/overlays?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.