Connected Supabase with Wized

Wized
1

Hi,

I am trying to execute a REST API call to Supabase in Wize. Did all the necessary things (and double checked), but after 4 hours I still get a 500 status response. I just want to setup the connection. It drives me crazy. Is there a support line who can help me?

2

Hey @martijn, four hours on this is rough — let’s get it sorted. :sweat_smile:

The 500 “Failed to Fetch” error is almost always a CORS issue. When Wized makes a REST API call directly from the browser to Supabase, the browser’s security restrictions can block the request before it even reaches Supabase. So the 500 doesn’t mean Supabase rejected your config — it means the request never got there in the first place.

The cleanest fix is switching to Wized’s native Supabase integration instead of a raw REST request. Wized routes those calls through their servers, which bypasses the CORS problem entirely.

If you need to stick with the REST approach, here’s what to check:

  1. Use Wized Secrets for your API key — Store your Supabase anon key as a Secret in the Data Store, then reference it in your header via the function editor (return s.your_secret_name). This also routes through Wized’s servers, which sidesteps CORS.
  2. Check your endpoint URL — The endpoint should be the relative path only (e.g., /rest/v1/[your-table]), not the full URL. The base URL gets set at the app level during initial integration setup.
  3. Verify your headers — Supabase requires both an apikey header and Authorization: Bearer [your-key]. Make sure both are present.
  4. Check the response body in Wized — Open the request in the Data Store panel and look at the Body tab. Supabase sometimes returns more detail there than just the status code.

Could you share a screenshot of your request config — the endpoint, headers, and body setup? That’ll help us pinpoint exactly what’s going wrong. :folded_hands:

3

@Support-Finn

Hi, it works now. There was something not updated. Thank you!