> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/configuration.md).

# Configuration

- [Overview](https://docs.serverlessapigateway.com/configuration/overview.md): Complete configuration reference for the Serverless API Gateway. Covers servers, CORS, JWT authorizer, paths, service binding, and wrangler setup.
- [Servers](https://docs.serverlessapigateway.com/configuration/servers.md): Define upstream server aliases and URLs for the Serverless API Gateway. Route API traffic to backend services via config-driven server entries.
- [Service Binding](https://docs.serverlessapigateway.com/configuration/service-binding.md): Configure Cloudflare Workers service bindings in Serverless API Gateway. Bind API routes to Worker services for modular, edge-native serverless integrations.
- [Paths](https://docs.serverlessapigateway.com/configuration/paths.md): Configure path-based API routing in the Serverless API Gateway. Define methods, endpoints, auth, mappings, and server integrations per route.
- [Add and Remove Prefix](https://docs.serverlessapigateway.com/configuration/add-and-remove-prefix.md): Add or remove URL path prefixes when proxying requests in the Serverless API Gateway. Rewrite or strip path segments before forwarding to upstream servers.
- [Authorizer](https://docs.serverlessapigateway.com/configuration/authorizer.md): Configure JWT authorization with HS256 for the Serverless API Gateway. Includes JOSE JWT error codes, claim validation failures, and fixes for common 401 token errors.
- [Authentication](https://docs.serverlessapigateway.com/configuration/authentication.md): Configure API gateway authentication with JWT, Auth0, and Supabase. Supports OAuth 2.0, OTP passwordless login, and token-based auth.
- [CORS](https://docs.serverlessapigateway.com/configuration/cors.md): Configure CORS (Cross-Origin Resource Sharing) for the Serverless API Gateway. Set allowed origins, methods, headers, and preflight cache.
- [Variable Mapping](https://docs.serverlessapigateway.com/configuration/variable-mapping.md): Map and transform request headers, query params, and JWT claims in the Serverless API Gateway. Dynamic variable templates for edge routing.
- [Priority Variables](https://docs.serverlessapigateway.com/configuration/priority-variables.md): Variable resolution priority in Serverless API Gateway mappings. Local config variables override global variables per endpoint.
- [Integrations](https://docs.serverlessapigateway.com/configuration/integrations.md): Serverless API Gateway integrations for authentication, proxying, and service bindings. Connect Auth0, Supabase, HTTP backends, and Cloudflare services.
- [Auth0](https://docs.serverlessapigateway.com/configuration/auth0.md): Configure Auth0 with Serverless API Gateway. Set up Auth0 client ID, client secret, JWKS, callback URLs, and OAuth 2.0 authorization flow.
- [Supabase OTP](https://docs.serverlessapigateway.com/configuration/supabase-otp.md): Supabase OTP for Serverless API Gateway. Fix magic link vs OTP issues, configure signInWithOtp, email templates, phone OTP, and verify flows on Cloudflare Workers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.serverlessapigateway.com/configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.