Last updated: November 16, 2026
An API gateway is a single entry point that sits in front of your backend services and handles the cross-cutting jobs every API needs: routing requests, authenticating callers, enforcing rate limits, transforming requests and responses, and logging traffic.
You usually need one once you expose APIs to customers or partners, or run more than a handful of services. A single internal service may not need one yet. For options, see the best API gateways.
| Function | What It Means |
|---|---|
| Routing | Sends each request to the right service |
| Authentication | Checks API keys, OAuth tokens or JWTs |
| Rate limiting | Protects services from overload and abuse |
| Transformation | Changes headers, payloads or protocols |
| Observability | Logs, metrics and traces for every call |
| Caching | Serves repeated responses faster |
It enforces security policies, but full protection also needs API security tools.
Slightly; well-tuned gateways add only milliseconds.
A gateway specialized for LLM traffic, with routing across model providers, caching and token cost controls.
Most production microservice systems use one at the edge.
API Management hub, Best API gateways, Kong vs Apigee vs AWS API Gateway, Best LLM API gateways and routers.