> 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/integrations.md). # Integrations - [Auth0](https://docs.serverlessapigateway.com/integrations/auth0-setup.md): Configure Auth0 when you need hosted identity, JWKS-backed verification, and callback flows at the gateway. This guide covers the full authorizer block, - [Auth0: JWKS vs JWKS URI](https://docs.serverlessapigateway.com/integrations/auth0-setup/auth0-jwks-vs-jwks-uri.md): Choose local JWKS or remote JWKS URI based on whether you want static config or dynamic key retrieval. A local \`jwks\` object bakes the key set into your config, - [Auth0 Callback Route](https://docs.serverlessapigateway.com/integrations/auth0-setup/auth0-callback-route.md): Use the callback integration to exchange authorization codes for tokens without moving the flow into your upstream. The gateway handles the code-to-token - [Auth0 Login Redirect Route](https://docs.serverlessapigateway.com/integrations/auth0-setup/auth0-login-redirect-route.md): Use the redirect integration when the gateway should initiate login instead of the frontend hardcoding the authorize URL. The gateway constructs the Auth0 - [Auth0 Userinfo Route](https://docs.serverlessapigateway.com/integrations/auth0-setup/auth0-userinfo-route.md): Expose a profile endpoint through the gateway when the client needs a normalized entry point for Auth0 user info. The gateway proxies the userinfo request to - [Auth0 Refresh Token Route](https://docs.serverlessapigateway.com/integrations/auth0-setup/auth0-refresh-token-route.md): Handle refresh token exchange through the gateway when you want one edge-managed auth surface. The gateway sends the refresh token to Auth0's token endpoint and - [Auth0 Error Handling](https://docs.serverlessapigateway.com/integrations/auth0-setup/auth0-error-handling.md): Use this page to understand upstream, network, and validation errors returned by the Auth0 integration. The gateway surfaces Auth0 API errors, network timeouts, - [Supabase](https://docs.serverlessapigateway.com/integrations/supabase-jwt-protected-routes.md): Protect routes with Supabase-issued tokens when your app already uses Supabase Auth as the identity provider. The gateway validates Supabase JWTs using the - [Supabase Email OTP](https://docs.serverlessapigateway.com/integrations/supabase-jwt-protected-routes/supabase-email-otp.md): Use the email OTP integration when you want passwordless email auth behind one edge endpoint. The gateway sends a POST request to Supabase's GoTrue API with the - [Supabase Phone OTP](https://docs.serverlessapigateway.com/integrations/supabase-jwt-protected-routes/supabase-phone-otp.md): Use the phone OTP integration when your product authenticates users by SMS. The flow is identical to email OTP, but the client sends a phone number instead of - [Supabase Verify OTP](https://docs.serverlessapigateway.com/integrations/supabase-jwt-protected-routes/supabase-verify-otp.md): Verify OTP codes through the gateway so the client only talks to one auth surface. The client sends the OTP code and the email or phone number to the verify - [Supabase Alternative Email Auth Path](https://docs.serverlessapigateway.com/integrations/supabase-jwt-protected-routes/supabase-alt-email-auth.md): Use the alternative email path only when the default OTP flow does not match your project behavior. Some Supabase configurations require a different GoTrue - [Supabase Required Environment Variables](https://docs.serverlessapigateway.com/integrations/supabase-jwt-protected-routes/supabase-required-env-vars.md): Set the required Supabase environment variables before you test any passwordless auth route. The gateway needs \`SUPABASE\_URL\`, \`SUPABASE\_ANON\_KEY\`, and - [Supabase Troubleshooting: Magic Link vs OTP](https://docs.serverlessapigateway.com/integrations/supabase-jwt-protected-routes/supabase-troubleshooting-magic-link-vs-otp.md): Debug the common mismatch where Supabase sends magic links instead of numeric OTP codes. The gateway's verify integration expects a numeric code, but Supabase --- # 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, and the optional `goal` query parameter: ``` GET https://docs.serverlessapigateway.com/integrations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.