iOS · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for App Store Connect End User License Agreements API

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

What the actions change

x-apievangelist-phrasing

Targets 7

$.info
$.paths['/v1/endUserLicenseAgreements'].post
$.paths['/v1/endUserLicenseAgreements/{id}'].get
$.paths['/v1/endUserLicenseAgreements/{id}'].delete
$.paths['/v1/endUserLicenseAgreements/{id}'].patch
$.paths['/v1/endUserLicenseAgreements/{id}/relationships/territories'].get
$.paths['/v1/endUserLicenseAgreements/{id}/territories'].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 App Store Connect End User License Agreements API
  version: 1.0.0
extends: openapi/ios-enduserlicenseagreements-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: 6
- target: $.paths['/v1/endUserLicenseAgreements'].post
  update:
    x-apievangelist-phrasing:
      intent: Add a custom EULA to an app
      effect: write
      questions:
      - How do I replace Apple's standard license agreement with my own EULA?
      - Can I attach a custom end user license agreement that applies to specific territories?
      instructions:
      - text: Create a custom end user license agreement with {data}.
        slots:
          data: requestBody.data
      - text: Add my own EULA text and territories to the app using {data}.
        slots:
          data: requestBody.data
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v1/endUserLicenseAgreements/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a custom EULA
      effect: read
      questions:
      - What license agreement text does my app currently use?
      - Can I read a specific custom EULA record?
      instructions:
      - text: Show end user license agreement {id}.
        slots:
          id: path.id
      - text: Fetch the agreement text of custom EULA {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v1/endUserLicenseAgreements/{id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a custom EULA
      effect: destructive
      questions:
      - Can I drop my custom license agreement and go back to the standard one?
      - What happens when I remove a custom EULA from my app?
      instructions:
      - text: Delete end user license agreement {id}.
        slots:
          id: path.id
      - text: Remove custom EULA {id} from the app.
        slots:
          id: path.id
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v1/endUserLicenseAgreements/{id}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update a custom EULA
      effect: write
      questions:
      - Can I edit the wording of my custom license agreement?
      - Is it possible to change which territories a custom EULA covers?
      instructions:
      - text: Update end user license agreement {id} with {data}.
        slots:
          id: path.id
          data: requestBody.data
      - text: Change the text or territories of custom EULA {id} to {data}.
        slots:
          id: path.id
          data: requestBody.data
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v1/endUserLicenseAgreements/{id}/relationships/territories'].get
  update:
    x-apievangelist-phrasing:
      intent: List territory IDs covered by a custom EULA
      effect: read
      questions:
      - Which territory IDs does a custom license agreement apply to?
      - Can I get just the territory references for a EULA?
      instructions:
      - text: List only the territory IDs covered by EULA {id}.
        slots:
          id: path.id
      - text: Return up to {limit} territory linkages for license agreement {id}.
        slots:
          id: path.id
          limit: query.limit
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v1/endUserLicenseAgreements/{id}/territories'].get
  update:
    x-apievangelist-phrasing:
      intent: List territories covered by a custom EULA
      effect: read
      questions:
      - In which countries do customers see my custom license agreement?
      - What currencies are used in the territories my EULA covers?
      instructions:
      - text: Show the full territories covered by end user license agreement {id}.
        slots:
          id: path.id
      - text: List every country where custom EULA {id} applies, with currency.
        slots:
          id: path.id
      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/ios-enduserlicenseagreements-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.