Microsoft Azure · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Microsoft Azure Sensor Mappings API

5 actions 5 updates phrasing extends openapi/microsoft-azure-sensormappings-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 5

$.info
$.paths['/sensor-mappings'].get
$.paths['/sensor-mappings/{sensorMappingId}'].get
$.paths['/sensor-mappings/{sensorMappingId}'].delete
$.paths['/sensor-mappings/{sensorMappingId}'].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 Microsoft Azure Sensor Mappings API
  version: 1.0.0
extends: openapi/microsoft-azure-sensormappings-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: 4
- target: $.paths['/sensor-mappings'].get
  update:
    x-apievangelist-phrasing:
      intent: List sensor mappings
      effect: read
      questions:
      - Which farm sensors are mapped to which parties and boundaries in Azure Data Manager for Agriculture?
      - Can I filter sensor mappings by sensor partner or boundary?
      instructions:
      - text: List all sensor mappings.
      - text: List sensor mappings for sensors {sensorIds} from partner {sensorPartnerIds}.
        slots:
          sensorIds: query.sensorIds
          sensorPartnerIds: query.sensorPartnerIds
      - text: Show sensor mappings attached to boundaries {boundaryIds} for parties {partyIds}.
        slots:
          boundaryIds: query.boundaryIds
          partyIds: query.partyIds
      method: generated
      generated: '2026-09-26'
- target: $.paths['/sensor-mappings/{sensorMappingId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a sensor mapping
      effect: read
      questions:
      - How do I check which party and boundary one sensor mapping points to?
      - What does a specific sensor mapping entity contain?
      instructions:
      - text: Get sensor mapping {sensorMappingId}.
        slots:
          sensorMappingId: path.sensorMappingId
      - text: Show the details of sensor mapping {sensorMappingId}.
        slots:
          sensorMappingId: path.sensorMappingId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/sensor-mappings/{sensorMappingId}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a sensor mapping
      effect: destructive
      questions:
      - How do I unlink a sensor from a party by deleting its mapping?
      - Can I remove a sensor mapping I created by mistake?
      instructions:
      - text: Delete sensor mapping {sensorMappingId}.
        slots:
          sensorMappingId: path.sensorMappingId
      - text: Remove the sensor mapping entity {sensorMappingId}.
        slots:
          sensorMappingId: path.sensorMappingId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/sensor-mappings/{sensorMappingId}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Create or update a sensor mapping
      effect: write
      questions:
      - How do I associate a partner sensor with a grower's field boundary?
      - Can I map one sensor to both a party and a boundary in a single request?
      instructions:
      - text: Map sensor {sensorId} from partner {sensorPartnerId} to party {partyId} as mapping {sensorMappingId}.
        slots:
          sensorId: requestBody.sensorId
          sensorPartnerId: requestBody.sensorPartnerId
          partyId: requestBody.partyId
          sensorMappingId: path.sensorMappingId
      - text: Attach sensor mapping {sensorMappingId} to boundary {boundaryId}.
        slots:
          sensorMappingId: path.sensorMappingId
          boundaryId: requestBody.boundaryId
      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-sensormappings-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.