Create a Supabase Client Per Request in SSR API Route

In SSR API Routes, you don’t have access to the supabase client that you’ve set up in your application. This will prevent you from sending authed requests to supabase even if you have a valid session or access token in your cookies.

The recommended solution is to create a new supabase client per request in your SSR API routes configured with the access token of the current user.

const supabase = createClient(
  { global: { 
      headers: {
        Authorization: `Bearer ${accessToken}`

Commit where I implemented this:


Notes mentioning this note

Join the Newsletter