# Amazon API Gateway HTTP API

> API Gateway HTTP and WebSocket APIs are the v2 surface, discovered from the apigateway:apis type on the six-hour Resource Explorer cycle. Coverage is inventory and cost attribution only: no recommendation rule, no schedule, and no delete workflow targets api-gateway-v2 today.

Source: https://zop.dev/integrations/aws/api-gateway-v2

---

API Gateway v2 covers two API types that share a control plane and almost nothing else. HTTP APIs are the leaner successor to REST, and WebSocket APIs hold long-lived bidirectional connections. Both arrive in the inventory under one resource type.

## Two very different APIs behind one type

An HTTP API bills per request, at a lower per-million rate than the REST equivalent, and offers a reduced feature set in exchange. A WebSocket API bills on two axes instead of one: messages transferred and connection minutes held open. The second axis is the one that surprises people, because a connection that sits open exchanging nothing still accrues minutes. Both land in the inventory as api-gateway-v2, so the type alone does not tell you which meter applies. The API name and its protocol in the console do.

## Inventory without a recommendation

No rule evaluates this type. There is no idle signal, no hygiene check, and no rightsizing lever registered against api-gateway-v2, and none is implied by the presence of RC-166 on its REST sibling. Coverage here is honest inventory: the API appears in resource lists, carries its tags, and participates in cost attribution and blast-radius views. Anything more would be a claim the engine cannot back.

## Nothing to schedule, nothing to delete

api-gateway-v2 appears in no schedulable set, so it is never offered a start or stop window. It is also absent from the delete workflow allowlist, which its REST sibling does belong to. A v2 API is therefore read-only from the platform's point of view: discovery observes it, and every change stays with you.

## Why the split matters when reading a bill

Because HTTP and WebSocket usage bills differently, a single line item for API Gateway spend can hide two unrelated stories. A month where cost rose while request counts fell usually means WebSocket connection minutes grew, not that requests got more expensive. Splitting the AWS cost data by usage type separates the request charge from the connection-minute charge, and the inventory list tells you which APIs could be responsible for each.