> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
> Use this file to discover all available pages before exploring further.
# API Gateway (REST)
> Operations, limits and service levels for API Gateway (REST) adapters with AWS origin APIs.
These terms describe the origin API served by the adapter, not direct calls to the target service. Management-request latency covers accepting and handling the API call; it does not promise that a cloud resource finishes provisioning within that time.
## Service level agreements
These tables show Tensor9's standard service levels and adapters whose standard terms are still being defined. Your signed agreement determines the SLAs, covered adapters and operations, limits, remedies and support terms that apply to your deployment.
Listed terms cover requests sent through this service adapter. They do not cover direct connections to the target service or replace the cloud provider's own SLA. Each origin-to-target pair has its own terms or an explicit pending status.
See the [SLA tables](/cloud-adapter/support/service-adapter-slas), [measurement rules](/cloud-adapter/support/service-levels), and [scaling conditions](/cloud-adapter/support/scaling-and-limits).
### API Gateway (REST) to Envoy
| SLA | Service level | What is covered | Conditions |
| ----------------------------------------------- | ----------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| API Gateway authoring reads | 5 ms monthly p99 | `aws::1.0.0::api-gateway::v1`: `GetAuthorizer`, `GetAuthorizers`, `GetIntegration`, `GetMethod`, `GetResource`, `GetResources`, `GetRestApi`, `GetRestApis` | Point read or at most 100 returned records; configuration at most 1 MiB. These targets apply only to a deployed API Gateway REST adapter on Envoy named in a signed agreement. Envoy packet forwarding and integrated function execution are separate from management-request processing. |
| API, route, integration and authorizer mutation | 12 ms monthly p99 | `aws::1.0.0::api-gateway::v1`: `CreateAuthorizer`, `CreateResource`, `CreateRestApi`, `DeleteAuthorizer`, `DeleteIntegration`, `DeleteMethod`, `DeleteResource`, `DeleteRestApi`, `PutIntegration`, `PutMethod`, `UpdateAuthorizer`, `UpdateRestApi` | One resource per call; API configuration at most 1 MiB. These targets apply only to a deployed API Gateway REST adapter on Envoy named in a signed agreement. Envoy packet forwarding and integrated function execution are separate from management-request processing. |
| Deployment and stage coordination | 25 ms monthly p99 | `aws::1.0.0::api-gateway::v1`: `CreateDeployment`, `CreateStage`, `DeleteStage`, `GetDeployment`, `GetDeployments`, `GetStage`, `GetStages`, `UpdateStage` | at most 100 routes and at most 20 authorizers/integrations; provider propagation separate. These targets apply only to a deployed API Gateway REST adapter on Envoy named in a signed agreement. Envoy packet forwarding and integrated function execution are separate from management-request processing. |
| Correct request handling | 99.9% per calendar month | `aws::1.0.0::api-gateway::v1`: `GetAuthorizer`, `GetAuthorizers`, `GetIntegration`, `GetMethod`, `GetResource`, `GetResources`, `GetRestApi`, `GetRestApis`, `CreateAuthorizer`, `CreateResource`, `CreateRestApi`, `DeleteAuthorizer`, `DeleteIntegration`, `DeleteMethod`, `DeleteResource`, `DeleteRestApi`, `PutIntegration`, `PutMethod`, `UpdateAuthorizer`, `UpdateRestApi`, `CreateDeployment`, `CreateStage`, `DeleteStage`, `GetDeployment`, `GetDeployments`, `GetStage`, `GetStages`, `UpdateStage` | The request uses an operation and request shape that this adapter profile lists as available, and stays within the limits in the service page and your signed agreement. A target-service failure does not count as an adapter failure when Tensor9 correctly returns that failure to the caller. These targets apply only to a deployed API Gateway REST adapter on Envoy named in a signed agreement. Envoy packet forwarding and integrated function execution are separate from management-request processing. |
| Documented adapter behavior | Preserve the supported behavior documented for this adapter | `aws::1.0.0::api-gateway::v1`: `GetAuthorizer`, `GetAuthorizers`, `GetIntegration`, `GetMethod`, `GetResource`, `GetResources`, `GetRestApi`, `GetRestApis`, `CreateAuthorizer`, `CreateResource`, `CreateRestApi`, `DeleteAuthorizer`, `DeleteIntegration`, `DeleteMethod`, `DeleteResource`, `DeleteRestApi`, `PutIntegration`, `PutMethod`, `UpdateAuthorizer`, `UpdateRestApi`, `CreateDeployment`, `CreateStage`, `DeleteStage`, `GetDeployment`, `GetDeployments`, `GetStage`, `GetStages`, `UpdateStage` | A deployment is an immutable complete revision, stages select one revision atomically, dependent routes never become public when an authorizer is removed, and invocation authority remains separate from caller authority. Unsupported private links or custom-domain shapes fail explicitly. |
| Endpoint reachability | 99.9% per calendar month | Adapter endpoint reachability | The agreed production deployment has healthy target connectivity and receives a valid adapter health probe. This measures the adapter endpoint, not the target provider's service. These targets apply only to a deployed API Gateway REST adapter on Envoy named in a signed agreement. Envoy packet forwarding and integrated function execution are separate from management-request processing. |
| Adapter autoscaling and limits | Automatic scaling within the workload and deployment limits in your agreement | Adapter behavior across requests | Your agreement states the maximum request rate, burst size, request and response sizes, concurrency, and target calls per request. Tensor9 maintains adapter capacity inside that envelope. Target-service quotas and capacity are separate. |
**Deployment availability.** These targets apply only to a deployed API Gateway REST adapter on Envoy named in a signed agreement. Envoy packet forwarding and integrated function execution are separate from management-request processing.
**What Tensor9 covers.** These service levels cover the adapter between the origin API and target API. They do not replace the target provider's SLA.
**How latency is counted.** Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded.
**Which terms apply.** Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.
#### What this adapter does
Authoring calls validate and store API, route, integration, authorizer, deployment and stage records. Deployment materialization onto envoy::1.0.0::proxy is coordinated separately. For served requests, ingress parsing, authorization callouts, Lambda-event construction and response conversion remain adapter work; backend integration execution is separately spanned.
#### How the latency targets were chosen
**API Gateway authoring reads: 5 ms monthly p99.** `GetAuthorizer`, `GetAuthorizers`, `GetIntegration`, `GetMethod`, `GetResource`, `GetResources`, `GetRestApi`, `GetRestApis`. Indexed control-state read and bounded response encoding.
**API, route, integration and authorizer mutation: 12 ms monthly p99.** `CreateAuthorizer`, `CreateResource`, `CreateRestApi`, `DeleteAuthorizer`, `DeleteIntegration`, `DeleteMethod`, `DeleteResource`, `DeleteRestApi`, `PutIntegration`, `PutMethod`, `UpdateAuthorizer`, `UpdateRestApi`. Validation and one durable authoring-state mutation.
**Deployment and stage coordination: 25 ms monthly p99.** `CreateDeployment`, `CreateStage`, `DeleteStage`, `GetDeployment`, `GetDeployments`, `GetStage`, `GetStages`, `UpdateStage`. Immutable snapshot construction and reconciliation scheduling.
Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.
#### What counts toward latency
For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter's own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it.
For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request's adapter duration first, then the monthly p99. Do not subtract one service's p99 from another's. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.
#### Availability and failures
The 99.9% request target measures correct adapter handling, not the percentage of application calls that return success. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures count even when the target is healthy.
With 1,000,000 eligible calls in a month, a 99.9% target permits at most 1,000 adapter-attributable failures. Endpoint probes have their own denominator. Correctness defects remain actionable even when the monthly availability percentage is met.
#### Scaling and target-service capacity
Authoring scales by API while mutations to one API are generation ordered. Reads and bounded lists scale horizontally. Qualification fixes routes, integrations, authorizers, stages, document bytes and list-page size; deployment trials include materialization fan-out without folding provider propagation time into local processing.
Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service's capacity with Tensor9's help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.
#### Data and behavior guarantees
A deployment is an immutable complete revision, stages select one revision atomically, dependent routes never become public when an authorizer is removed, and invocation authority remains separate from caller authority. Unsupported private links or custom-domain shapes fail explicitly.
#### Example and diagnosis
CreateDeployment snapshots 50 routes and five authorizers. The coordinated-write target covers snapshot construction and durable admission. Writing those routes and policies to API Management or Google API Gateway is measured as propagation; stage traffic changes only when the selected revision is ready under the profile contract.
Use `tensor9 explain` and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider's latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.