Skip to main content

API Gateway

The Adeptia API Gateway receives inbound API requests to the Adeptia platform, handling client context forwarding so that downstream services have the information they need to process each request correctly.

What the API Gateway does​

When an external client sends a request to Adeptia, the API Gateway receives it first. Along the way, the gateway captures and forwards relevant client context, such as the originating client address, so that downstream services have the information they need.

The gateway also processes callback addresses. When a request includes a callback destination, the gateway sets that destination to the scheme, host, and port of the incoming request.

How requests flow through the gateway​

A typical inbound request follows this path:

  1. The client sends a request to the Adeptia platform.
  2. The API Gateway receives the request.
  3. Client address information is captured and attached so downstream services can identify the caller.
  4. If the request includes a callback address, the gateway resolves it to the scheme, host, and port of the incoming request.
  5. The request is passed along the processing chain.