Passing custom headers with the new API keys

It seems like custom headers are being stripped when passed with the new api keys, publishable or not. Ideas, suggestions?

   headers: {
      'apikey': <key>,
      'x-custom-header': <header>,
      'Content-Type': 'application/json',
    },

   headers: {
      'apikey': <key>,
      'x-custom-header': <header>,
      'Content-Type': 'application/json',
    },

   headers: {
      'apikey': <key>,
      'x-custom-header': <header>,
      'Content-Type': 'application/json',
    },

   headers: {
      'apikey': <key>,
      'x-custom-header': <header>,
      'Content-Type': 'application/json',
    },

TIA!

Supabase Join

Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.

44,406Members

View on Discord

Similar Threads

Local Setup with NEW API keys

SSupabase / help-and-questions

4mo ago

Migrating to the new API keys

SSupabase / help-and-questions

5mo ago

New api keys issues

SSupabase / help-and-questions

2w ago

New API keys not working

SSupabase / help-and-questions

2mo ago

Similar Threads

Was this page helpful?

Communities Docs About Terms Privacy