Your Supabase API Key. This can be your Anon or Service Role key. If you have RLS enabled, and want the current user to define access permissions use the Anon key. To give comnoco full access as a backend process, use the Service Role key. We recommend you set this as a system secret.
The Access Token (JWT) of a logged-in Supabase user, if provided, this will be used to determine the user's permissions (data returned) as set by RLS. Will remove the `Bearer` prefix from an auth header if necessary.
Add your own parameters to send as part of the query URL (eg: id=eq.1). If you have defined a Query Builder output this field it will be added to the end of the URL.
Catch errors from the Supabase call as a Data Structure and return them as the response value to enable manual error handling. If turned on errors will not get caught in a Try-Catch block.
Switch schema on your Supabase project, defaults to 'public'. See https://supabase.com/docs/guides/api/using-custom-schemas for a guide on custom schemas.