Microsoft Azure · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Microsoft Azure Azure Fluid Relay Fluid Relay Servers API

9 actions 9 updates phrasing extends openapi/microsoft-azure-fluidrelayservers-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Microsoft Azure's API. It is a proposal applied on top of the contract, not a document Microsoft Azure publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 9

$.info
$.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}'].get
$.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}'].put
$.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}'].delete
$.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}'].patch
$.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}/regenerateKey'].post
$.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}/getKeys'].post
$.paths['/subscriptions/{subscriptionId}/providers/Microsoft.FluidRelay/fluidRelayServers'].get
$.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers'].get

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 Microsoft Azure Azure Fluid Relay Fluid Relay Servers API
  version: 1.0.0
extends: openapi/microsoft-azure-fluidrelayservers-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: 8
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a Fluid Relay server
      effect: read
      questions:
      - What are the settings of my Azure Fluid Relay server?
      - Can I look up one Fluid Relay server by name in a resource group?
      instructions:
      - text: Get Fluid Relay server {server} in resource group {group}, subscription {subscription}.
        slots:
          server: path.fluidRelayServerName
          group: path.resourceGroup
          subscription: path.subscriptionId
      - text: Show the configuration of Fluid Relay server {server}.
        slots:
          server: path.fluidRelayServerName
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}'].put
  update:
    x-apievangelist-phrasing:
      intent: Create or replace a Fluid Relay server
      effect: write
      questions:
      - How do I stand up a Fluid Relay server for real-time collaboration in my app?
      - Can I give a new Fluid Relay server a managed identity when I create it?
      instructions:
      - text: Create Fluid Relay server {server} in group {group}, subscription {subscription} with properties {properties}.
        slots:
          server: path.fluidRelayServerName
          group: path.resourceGroup
          subscription: path.subscriptionId
          properties: requestBody.properties
      - text: Provision relay server {server} using managed identity {identity}.
        slots:
          server: path.fluidRelayServerName
          identity: requestBody.identity
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a Fluid Relay server
      effect: destructive
      questions:
      - Can I remove a Fluid Relay server I no longer use?
      - What deletes a Fluid Relay server from my resource group?
      instructions:
      - text: Delete Fluid Relay server {server} from resource group {group}, subscription {subscription}.
        slots:
          server: path.fluidRelayServerName
          group: path.resourceGroup
          subscription: path.subscriptionId
      - text: Tear down the relay server named {server}.
        slots:
          server: path.fluidRelayServerName
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update a Fluid Relay server's tags or identity
      effect: write
      questions:
      - Can I just change the tags on a Fluid Relay server without redeploying it?
      - Is it possible to switch the managed identity on an existing Fluid Relay server?
      instructions:
      - text: Set tags {tags} on Fluid Relay server {server} in group {group}, subscription {subscription}.
        slots:
          tags: requestBody.tags
          server: path.fluidRelayServerName
          group: path.resourceGroup
          subscription: path.subscriptionId
      - text: Change the managed identity of existing relay server {server} to {identity}.
        slots:
          server: path.fluidRelayServerName
          identity: requestBody.identity
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}/regenerateKey'].post
  update:
    x-apievangelist-phrasing:
      intent: Regenerate a Fluid Relay server key
      effect: destructive
      questions:
      - How do I rotate the primary or secondary key on my Fluid Relay server?
      - Does regenerating a Fluid Relay key invalidate tokens signed with the old one?
      instructions:
      - text: Regenerate the {key_name} key of Fluid Relay server {server} in group {group}, subscription {subscription}.
        slots:
          key_name: requestBody.keyName
          server: path.fluidRelayServerName
          group: path.resourceGroup
          subscription: path.subscriptionId
      - text: Rotate key {key_name} on relay server {server}.
        slots:
          key_name: requestBody.keyName
          server: path.fluidRelayServerName
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers/{fluidRelayServerName}/getKeys'].post
  update:
    x-apievangelist-phrasing:
      intent: Get the keys of a Fluid Relay server
      effect: read
      questions:
      - Where can I read the primary and secondary keys for my Fluid Relay server?
      - Can I fetch Fluid Relay keys to sign tokens without rotating them?
      instructions:
      - text: Get the current keys for Fluid Relay server {server} in group {group}, subscription {subscription}.
        slots:
          server: path.fluidRelayServerName
          group: path.resourceGroup
          subscription: path.subscriptionId
      - text: Read the primary and secondary keys of relay server {server}.
        slots:
          server: path.fluidRelayServerName
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/providers/Microsoft.FluidRelay/fluidRelayServers'].get
  update:
    x-apievangelist-phrasing:
      intent: List Fluid Relay servers in a subscription
      effect: read
      questions:
      - Which Fluid Relay servers do I have across my whole subscription?
      - Is there a subscription-wide list of Fluid Relay servers?
      instructions:
      - text: List all Fluid Relay servers in subscription {subscription}.
        slots:
          subscription: path.subscriptionId
      - text: Inventory every relay server across my subscription.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.FluidRelay/fluidRelayServers'].get
  update:
    x-apievangelist-phrasing:
      intent: List Fluid Relay servers in a resource group
      effect: read
      questions:
      - What Fluid Relay servers are deployed in one resource group?
      - Can I narrow the Fluid Relay server list to a single resource group?
      instructions:
      - text: List Fluid Relay servers in resource group {group}, subscription {subscription}.
        slots:
          group: path.resourceGroup
          subscription: path.subscriptionId
      - text: Show the relay servers inside group {group}.
        slots:
          group: path.resourceGroup
      method: generated
      generated: '2026-09-26'

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/microsoft-azure-fluidrelayservers-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.

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