Microsoft Entra ID (formerly Azure AD) · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Identity.SignIns Invitations.directory Object API

4 actions 4 updates phrasing extends openapi/azure-ad-invitations-directoryobject-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Microsoft Entra ID (formerly Azure AD)'s API. It is a proposal applied on top of the contract, not a document Microsoft Entra ID (formerly Azure AD) publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 4

$.info
$.paths['/invitations/invitedUserSponsors'].get
$.paths['/invitations/invitedUserSponsors/{directoryObject-id}'].get
$.paths['/invitations/invitedUserSponsors/$count'].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 Identity.SignIns Invitations.directory Object API
  version: 1.0.0
extends: openapi/azure-ad-invitations-directoryobject-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: 3
- target: $.paths['/invitations/invitedUserSponsors'].get
  update:
    x-apievangelist-phrasing:
      intent: List sponsors of invited guest users
      effect: read
      questions:
      - Which users or groups are sponsoring the guests we've invited?
      - Can I filter the list of invited-user sponsors to just groups?
      - Who is responsible for our guest users' privileges in the tenant?
      instructions:
      - text: List the sponsors of invited users.
      - text: List invited-user sponsors matching {filter}.
        slots:
          filter: query.$filter
      method: generated
      generated: '2026-10-01'
- target: $.paths['/invitations/invitedUserSponsors/{directoryObject-id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get one sponsor of an invited user
      effect: read
      questions:
      - How do I look up the details of a single guest sponsor by its object id?
      - What information is returned for one specific invited-user sponsor?
      instructions:
      - text: Get invited-user sponsor {directoryObject}.
        slots:
          directoryObject: path.directoryObject-id
      - text: Show the details of guest sponsor {directoryObject}.
        slots:
          directoryObject: path.directoryObject-id
      method: generated
      generated: '2026-10-01'
- target: $.paths['/invitations/invitedUserSponsors/$count'].get
  update:
    x-apievangelist-phrasing:
      intent: Count invited-user sponsors
      effect: read
      questions:
      - How many sponsors are assigned to invited guest users?
      - Can I get just a count of guest sponsors that match a filter?
      instructions:
      - text: Count the invited-user sponsors.
      - text: Count the guest sponsors matching {filter}.
        slots:
          filter: query.$filter
      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/azure-ad-invitations-directoryobject-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.