Appearance
Xano errors and FAQs
Most Xano issues come from one of three places: the API documentation of your API group, where the request runs (browser or WeWeb server), or the sign in setup. This page lists the most common symptoms and how to fix them.
Common pitfalls
The API group or its endpoints don't appear
WeWeb reads your endpoints and their inputs from the API documentation that Xano generates for each API group. If that documentation is broken, WeWeb can't list them.
Open the API documentation of the group in Xano. If it doesn't load, fix the endpoint that breaks it (often an empty input or variable), then click the refresh button next to API Group or Endpoint in WeWeb.
Xano can also refuse to send the documentation for a few seconds when it's requested too often. Wait a moment, then refresh.
The instances or workspaces don't load
The Meta API Key is wrong, expired, or doesn't have access to the instance. Create a new Metadata API key in your Xano account settings, paste it again, then click the refresh button next to Instance.
Requests fail after adding a custom domain
Custom Domain must be a full address, including https://, for example https://api.my-domain.com. Without it, requests fail or return unexpected results.
The editor and the published app don't return the same data
The connection has separate settings for each environment. Check the Instance, Workspace, Custom Domain, and branching settings of each environment in the Environment selector of the connection.
Branch or data source changes have no effect
X-Branch and X-Data-Source are only sent when Branching is Enabled. Enable it in the environment you're using, then fill in the fields.
An endpoint answers 401, but works for signed-in users in the app
The request reached Xano without a session. This happens when:
- The table is fetched by the WeWeb server (
Fetch all views via the frontend (advanced)is off). Bind anAuthorizationheader in the view, or turn the toggle on. Learn more → - The request uses a second Xano connection. Only the connection used for sign in carries the session.
- You test a backend workflow from the editor. A test run has no signed-in user.
A 401 can also come from WeWeb: if your table or API Endpoint requires a signed-in user in its Security settings, check that the user is set on the backend too. Learn more about the hybrid setup →
An endpoint answers 404
Check URL Params first. If a part of the path in curly braces, such as {job_id}, has no value, it stays as it is in the address, and Xano can't find the endpoint.
A filter or page number has no effect
A Xano endpoint ignores any input it doesn't declare. Add the input to the endpoint in Xano, refresh Query Parameters in WeWeb, then bind it.
For POST, PUT, PATCH, and DELETE endpoints, WeWeb sends the Body and ignores Query Parameters.
Updating a record resets other fields
Xano's default edit endpoints replace the whole record. Send every field of the record, not only the one that changed.
The user signs in, but looks signed out
Authenticate stores the session, but doesn't set the user. Create a workflow on the On user load trigger that retrieves the user from Xano and ends with Set User. Learn how →
Error handling
When Xano answers with an error, the API Request action fails with the HTTP status and, when Xano sends one, its error code. The table below lists the errors you'll see most often.
| Error code and type | Reason |
|---|---|
| 400 Bad Request | An input is missing or has the wrong format. Check the values you send against the inputs of the endpoint. |
401 Unauthorized (ERROR_CODE_UNAUTHORIZED) | The endpoint requires authentication and the request has no valid session. See the 401 pitfall. |
403 Forbidden (ERROR_CODE_ACCESS_DENIED) | The user doesn't have access, or a one-time code (for example during a social sign in) was already used or expired. |
404 Not Found (ERROR_CODE_NOT_FOUND) | The record or the endpoint doesn't exist. Check URL Params and the record id. |
429 Too Many Requests (ERROR_CODE_TOO_MANY_REQUESTS) | Your Xano plan's request limit was reached. Send fewer requests, or upgrade your Xano plan. |
| 500 Internal Server Error | Something failed inside your Xano endpoint. Check the request history of the endpoint in Xano. |
FAQs
Can I use Xano as both my data source and my Authentication System?
Yes. Connect Xano in the Integrations subtab of Data & API for tables and workflows, and choose Xano in the Authentication subtab if you want Xano to handle sign in.
Can I use POST endpoints as table data sources?
No. Xano tables only use GET endpoints. To create, update, or delete records, use the API Request action in a workflow.
Do I need to send the auth token myself?
Not in most cases. When Xano is your Authentication System, WeWeb sends the user's session with API Request actions and with tables fetched from the browser. The exception is a table fetched by the WeWeb server: add the Authorization header to its view.
Can I stream a Xano response in a backend workflow?
No. Stream Response is only available in Interface workflows. In backend workflows, the action waits for the full response.
Can I use Xano Realtime?
Yes, with a small piece of code in a Custom JavaScript action: there is no built-in Xano Realtime action yet. See the Xano Realtime recipes →
Can users sign in with Google or another social provider?
Yes, if your Xano workspace has the OAuth endpoints for that provider (installed from the Xano marketplace). Call them with API Request in Interface workflows, and end with Authenticate, like any other sign in. Learn how →