Invoke a deployed Supabase Edge Function over HTTPS at https://{project_ref}.supabase.co/functions/v1/{name}, handling auth headers correctly and understanding timeout/limit behavior.

Documented steps

1. Call the deployed function: curl --request POST 'https://{project_ref}.supabase.co/functions/v1/hello-world' --header 'apikey: PUBLISHABLE_KEY' --header 'Content-Type: application/json' --data '{"name":"Functions"}' — the publishable key is under Settings > API Keys.
2. Or via supabase-js: const { data, error } = await supabase.functions.invoke('hello-world', { body: { name: 'Functions' } }).
3. Locally (via `supabase functions serve`), the same function is reachable at http://127.0.0.1:54321/functions/v1/hello-world using the local publishable key from `supabase status`.
4. By default verify_jwt = true for every function, so the platform gateway validates the caller's Authorization/apikey before your handler code runs at all.
5. To allow calls without any Supabase credential (e.g. an external webhook), set in supabase/config.toml: [functions.hello-world] verify_jwt = false, then redeploy; inside the handler use the withSupabase wrapper's (npm:@supabase/server) auth 'none' mode and verify the provider's own signature (e.g. Stripe's) yourself.
6. Inside a function, withSupabase supports auth modes: 'user' (user JWT on Authorization, RLS-scoped client), secret (secret key on apikey, admin client), publishable (publishable key on apikey), or 'none' — pick the modes matching your callers.
7. If the function sends no response within the 150s request idle timeout, the gateway returns 504; separately, CPU time is capped at 2s/request and memory at 256MB, with worker wall-clock limits of 150s (Free) / 400s (paid plans).
8. Docs: https://supabase.com/docs/guides/functions https://supabase.com/docs/guides/functions/auth https://supabase.com/docs/guides/functions/limits https://supabase.com/docs/guides/functions/quickstart