AWS Amazon API Gateway

Name: Amazon API Gateway API
Brand: Amazon API Gateway
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingapiKey120 EndpointsREST

For Agents

Create and manage REST APIs, resources, methods, integrations, deployments, custom domains, API keys, and usage plans on Amazon API Gateway through 120 operations.

Install Jentic One Beta

Connect the Amazon API Gateway to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon API Gateway, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Amazon API Gateway API.

Create and version REST APIs with resources, methods, and request and response models

Wire methods to AWS Lambda, HTTP backends, and AWS service integrations including IAM and Cognito authorisers

Promote API revisions through stages with stage variables and per-stage caching configuration

GET STARTED

Start building with Amazon API Gateway API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Amazon API Gateway, keeping it validated and agent-ready. Amazon API Gateway is a managed service for creating and operating REST and WebSocket APIs at any scale, fronting AWS Lambda, EC2-hosted services, and any HTTP backend. The control-plane API exposes 120 operations covering REST API definitions, resources, methods, integrations, deployments, stages, custom domain names, API keys, usage plans, authorizers, and documentation parts. Platform teams use it to drive infrastructure-as-code workflows that go beyond what CloudFormation exposes.

Use Cases

Patterns agents use Amazon API Gateway API for, with concrete tasks.

★ Programmatic REST API Provisioning

Platform teams use the API Gateway control plane to provision REST APIs without leaning on CloudFormation for every change. POST /restapis creates a new API, then POST /restapis/{restapi_id}/resources and PUT /restapis/{restapi_id}/resources/{resource_id}/methods/{http_method} build out paths and methods. CreateDeployment publishes the configuration to a named stage where it becomes live.

Call POST /restapis with name=orders-api, then POST /restapis/{id}/resources to create the /orders path, PUT a GET method on it, and POST /restapis/{id}/deployments to publish to the prod stage

API Key and Usage Plan Management

Product teams that monetise APIs use API Gateway's usage plans to assign per-customer rate limits and quotas. POST /apikeys creates a key, POST /usageplans creates a plan with throttling and quota settings, and POST /usageplans/{usageplan_id}/keys attaches the key to the plan. Customers then send the key in the x-api-key header and API Gateway enforces limits at the edge.

Call POST /apikeys to create a key for customer-acme, POST /usageplans for a tier with 100 rps and 10000 daily quota, then POST /usageplans/{id}/keys to attach

Custom Domain Name Binding

Marketing and platform teams bind acquired domains to API stages so consumers see api.example.com instead of an AWS-owned URL. POST /domainnames registers the domain with an ACM certificate, then POST /domainnames/{domain_name}/basepathmappings maps a base path to a specific REST API stage. The same domain can host multiple APIs by base path.

Call POST /domainnames with domain=api.example.com and certificateArn from ACM, then POST /domainnames/api.example.com/basepathmappings mapping /v1 to the prod stage of restapi-id

AI Agent API Operator

An AI agent invoked through Jentic operates API Gateway to provision new APIs in response to a chat or ticket flow. The agent searches Jentic for the create-rest-api and create-deployment operations, executes them with the requested resources and integrations, and returns the resulting invoke URL. Jentic handles SigV4 signing, so the agent only deals with the structured payloads.

Search Jentic for create rest api on api gateway, execute it for the named API, then create resources, methods, and a deployment to a stage in sequence

Key Endpoints

120 endpoints — jentic publishes the only available openapi specification for amazon api gateway, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/restapis

Create a new REST API

GET

/restapis/{restapi_id}/resources

List the resources tree for a REST API

POST

/restapis/{restapi_id}/deployments

Create a deployment that publishes the API to a stage

POST

/apikeys

Create an API key

POST

/usageplans

Create a usage plan with throttling and quota

POST

/domainnames

POST

/restapis/{restapi_id}/authorizers

Create a Lambda, IAM, or Cognito authorizer for an API

POST

/restapis

Create a new REST API

GET

/restapis/{restapi_id}/resources

List the resources tree for a REST API

POST

/restapis/{restapi_id}/deployments

Create a deployment that publishes the API to a stage

POST

/apikeys

Create an API key

POST

/usageplans

Create a usage plan with throttling and quota

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access key id and secret access key for API Gateway are stored encrypted in the Jentic vault. Jentic performs SigV4 signing server side and supports STS temporary credentials, so the agent never sees the raw secret access key.

Intent-based discovery

Agents search Jentic with phrases like create rest api or create usage plan, and Jentic returns the matching API Gateway operation with its input schema, so the agent does not have to memorise the 120-operation surface area.

Time to first call

Direct integration: 3 to 5 days for SigV4 signing, retry logic, and the wide surface across REST APIs, resources, methods, deployments, and usage plans. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Amazon API Gateway API through Jentic.

Why is there no official OpenAPI spec for Amazon API Gateway?

AWS does not publish an OpenAPI specification for the API Gateway control plane; the official surface is the AWS SDKs and the Smithy model. Jentic generates and maintains this spec so that AI agents and developers can call Amazon API Gateway via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Amazon API Gateway control plane API use?

API Gateway uses AWS Signature Version 4 (SigV4) signed with an IAM access key id and secret access key, optionally with an STS session token. Through Jentic these credentials are stored encrypted in the vault and SigV4 signing is performed server side, so the agent never handles the raw secret access key.

Can I attach a custom domain to a specific stage with the Amazon API Gateway API?

Yes. POST /domainnames registers the custom domain with an ACM certificate, then POST /domainnames/{domain_name}/basepathmappings creates a mapping that routes a base path to a specific REST API id and stage. The same domain can host multiple APIs by giving each one a distinct base path.

What are the rate limits for the Amazon API Gateway control plane API?

API Gateway throttles control-plane operations per region; create and update operations like CreateRestApi and PutMethod have lower per-second limits than read operations like GetRestApis and GetResources. Throttling errors should be retried with exponential backoff. Data-plane request limits apply separately on the deployed APIs themselves.

How do I create a REST API with the Amazon API Gateway API through Jentic?

Install the SDK with pip install jentic, search Jentic for create rest api on api gateway, load the CreateRestApi operation schema, and execute it with a name and description. Jentic handles SigV4 signing and returns the new restapi_id, which you can then use to create resources, methods, and deployments.

Can I import an OpenAPI definition with the Amazon API Gateway API?

Yes. PUT /restapis/{restapi_id}#mode=import with an OpenAPI 2.0 or 3.0 document in the request body imports the definition into an existing API; POST /restapis with the body and mode=import creates a new API from an OpenAPI document. The same flow is used by the AWS Console import feature.

AWS Amazon API Gateway

Connect the Amazon API Gateway to your agent

Capabilities

Start building with Amazon API Gateway API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs