Logs

The Logs page helps you understand what happened when your app called your backend. You can inspect requests, responses, and errors for your API Endpoints and Table Views.

Use it when something “doesn’t work”, when you’re getting an unexpected error, or when you want to double‑check what data is being sent and returned.

What you can see in Logs

Each log entry represents one request processed by WeWeb’s backend.

You can see:

• Where it went: the API Endpoint or Table View (and the request path)
• Whether it worked: the status code (for example 200 or 500)
• How long it took: the execution time (how long the backend spent processing the request)
• What was sent: request Body, Url Parameters, Query Parameters, and Headers
• What came back: response Data and response Headers

Open the Logs page

1. Go to Data & API.
2. Click Logs in the top navigation.

Filter logs to find what you need

At the top of the page, you can narrow down the list.

Choose the environment

Use Select Environment to pick where you want to look:

• Editor (Testing)
• Staging (If enabled)
• Production

NOT SEEING THE REQUEST YOU EXPECT?

Make sure you’re looking at the same environment you’re testing.

For example, if you’re testing in preview, you’ll usually want Editor.

Choose what you’re logging

Use the type selector to choose what you want to inspect:

• All: Everything (including WeWeb system requests like health checks)
• Endpoints: Only your API Endpoints
• Table Views: Only requests that retrieve data from a table view

Depending on the type you choose, you’ll also see a dropdown:

• For Endpoints: Select an Endpoint
• For Table Views: Select a Table View

Search (All only)

When the type is All, you can use the Search… field to quickly find a request by name or path.

Date range

Use the start and end date fields to limit logs to a time window:

• Start date (defaults to Since Forever)
• End date (defaults to Now)

Refresh and load more

• Click Refresh to reload the latest logs.
• Click Load More at the bottom of the list to see older entries.

Inspect a log entry (request + response)

1. Select a log entry from the list on the left.
2. Review the Request section:
   • Switch between Body, Url Parameters, Query Parameters, and Headers.
3. Review the Response section:
   • Switch between Data and Headers.
4. Check the Execution time to spot slow requests.

JUMP TO THE SOURCE

If the log entry is for an API Endpoint or a Table View, you can click its name in the details panel to open it.

Common troubleshooting

“No logs found.”

This usually happens when the current filters don’t match anything. Try:

1. Switching to the correct environment (Editor vs Production)
2. Changing the type to All
3. Removing the date range (or widening it)
4. Clicking Refresh

I see a 401 or 403

These status codes often mean the request was blocked by access rules.

• Check the Security panel on the API Endpoint.
• If you’re using a Table View, check the view’s Access setting.

Learn more about securing API Endpoints →

I see a 500 error

A 500 usually means something went wrong while the backend was processing the request.

• Open the log entry and check the response Data to see the error message.
• If the request calls other actions (like HTTP request), check those action settings and try again.

FAQs

Does Logs show interface workflow logs?

No. The Logs page in Data & API is focused on backend requests (API Endpoints and Table Views).

To debug interface workflows, use the debugging tools for the Interface tab.

Why do I see requests I didn’t create?

When you use All, you may see WeWeb system requests (for example health checks).

Switch the type to Endpoints and select your API Endpoint to focus only on your own endpoints.

CONTINUE LEARNING

Learn how to debug workflows step‑by‑step using WeWeb’s debugger.

Intro to debugging →