Serverless API Gateway

Expose HTTP endpoints and webhooks on the gateway: path parameters, auth modes, rate limits, and optional custom domains all terminate on your serverless functions.

Run a serverless API gateway that exposes your functions as HTTP endpoints. Requests to /gw/{tenant}/your-path are routed to your functions.

How API gateway routing works

Open Gateway in the sidebar to define routes, methods, auth, and templates. The default workspace API is reached at /gw/<tenant-slug>/… where <tenant-slug> is your workspace slug. Named HTTP APIs (each has a subdomain host label) are reached at /gw/<label>/… so several APIs can coexist for one workspace.

Installations that enable custom domains can bind a hostname to a named HTTP API so public traffic does not use the default /gw/… prefix.

API gateway route configuration

Path parameters — /users/:id matches /users/42.
Wildcards — /site/** matches any sub-path.
Methods — GET, POST, PUT, PATCH, DELETE, or ANY.
Auth — Public, API Key, or Bearer Token per route.

Event Format

Choose between Simple (flat top-level fields) or AWS API Gateway v2 compatible format:

event

// Your Lambda receives an event like (simple gateway format; body is always a string or null):
{
  "httpMethod": "POST",
  "path": "/api/users",
  "headers": {
    "content-type": "application/json"
  },
  "queryStringParameters": {
    "page": "1"
  },
  "pathParameters": {
    "id": "123"
  },
  "body": "{\"name\":\"Alice\"}"
}

Response Transformation

In the Advanced Options you can configure:

Response Headers — Static headers added to every response.
Request Template — Transform the event before it reaches your function.
Response Template — Transform the function's response before sending it to the client.
Rate Limit — Requests per minute per route.