Amazon API Gateway · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Amazon API Gateway REST API Keys Base Path Mappings API

3 actions 3 updates phrasing extends openapi/aws-api-gateway-base-path-mappings-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Amazon API Gateway's API. It is a proposal applied on top of the contract, not a document Amazon API Gateway publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info
$.paths['/domainnames/{domain_name}/basepathmappings'].get
$.paths['/domainnames/{domain_name}/basepathmappings'].post

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 Amazon API Gateway REST API Keys Base Path Mappings API
  version: 1.0.0
extends: openapi/aws-api-gateway-base-path-mappings-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: 2
- target: $.paths['/domainnames/{domain_name}/basepathmappings'].get
  update:
    x-apievangelist-phrasing:
      intent: List a custom domain's base path mappings
      effect: read
      questions:
      - Which APIs and stages are mapped under my custom domain?
      - How do I see the base paths configured on a domain?
      instructions:
      - text: List base path mappings for domain {domain_name}.
        slots:
          domain_name: path.domain_name
      - text: Show which APIs are mapped under {domain_name}.
        slots:
          domain_name: path.domain_name
      method: generated
      generated: '2026-10-01'
- target: $.paths['/domainnames/{domain_name}/basepathmappings'].post
  update:
    x-apievangelist-phrasing:
      intent: Map a REST API to a custom domain path
      effect: write
      questions:
      - How do I serve my REST API under a path like /v1 on my custom domain?
      - Can I map a specific stage to my custom domain?
      instructions:
      - text: Map REST API {restApiId} to domain {domain_name}.
        slots:
          restApiId: requestBody.restApiId
          domain_name: path.domain_name
      - text: Map REST API {restApiId} stage {stage} to {domain_name} at base path {basePath}.
        slots:
          restApiId: requestBody.restApiId
          stage: requestBody.stage
          domain_name: path.domain_name
          basePath: requestBody.basePath
      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/aws-api-gateway-base-path-mappings-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.