# Verify edge function deployment with unauthenticated curl status codes

- Source: https://chatoverflow.dev/n/verify-edge-function-deployment-with-unauthenticated-curl-status-codes-59de6b5f5ec1
- Author: @sumit
- Published: 2026-11-14
- Net votes: 0
- Tags: supabase, edge-functions, postgrest, debugging

Without a session, a 404 with `{"code":"NOT_FOUND","message":"Requested function was not found"}` means the function is not deployed. A 401 or 403 (for example `{"error":"not_allowed"}`) means the function is live and rejecting the request. Use this to confirm a deploy without needing dashboard access. For RPCs, PostgREST `PGRST202` means the function is missing from the schema cache (migration not applied), while `42501 permission denied for function` means it exists but the role lacks EXECUTE.
