Connecting my WeWeb (SaaS) dashboard to my Xano databases

[AquarianAI89]

Hi WeWeb Community,

I’m building my very first SaaS product using WeWeb with Xano as my backend. I don’t have any coding or technical background — I’m learning everything as I go, and this is my first time setting up a login/signup flow.

Right now, I’m stuck on the login/signup page, and I keep getting a 401 error when I test it. I’ve tried to troubleshoot it myself, but I’m not sure what I’m missing or doing wrong.

Here’s what I’ve tried:
• I followed the WeWeb + Xano authentication tutorial step by step.
• I confirmed that the API endpoints from Xano are correct and connected.
• I bound the email and password fields to my form correctly.
• I made sure the inputs are being passed to the API request.
• I checked my Xano Auth settings and CORS — they look fine to me.

But I still get a 401 Unauthorized error when I try to log in or sign up. Since I’m new to all this, I’m not sure if it’s an issue with how I’m sending the request, the headers, or something I forgot to include.

If anyone can explain what might be causing this (in beginner-friendly terms ), I’d be super grateful. I’m really trying to push through and get this working!

Thanks so much in advance,
— Ashley

[iconic]

check your xano endpoint. is it a public endpoint like this

[avidflow]

Hi Ashley,

One way that I usually troubleshoot issues like this is to view the API request on the Xano side.

In Xano, you can access the Request history to see what Xano is actually receiving from your API call and what error it is sending back.

Also, in Weweb, can you expand the error you’re seeing, specifically, the response > data

If you could share the error, then that should lend a clue. For e.g. Xano may not receiving your email and password as inputs even though you think these are being sent and hence is returning a 401 (Unauthorized). It could also be that Xano isn’t receiving the API Bearer token in the request. This might happen if you’re using the REST API plugin (you have you to add an authentication header in your request manually) instead of the Xano plugin (has the authentication built into the plugin).

Best,
Sean