Testing with the API Debugger

The API Debugger lets Creators send test requests to a module and inspect the full execution without going through the production application. Use it to verify server-side logic, trace data changes, and debug API calls before publishing.

For the full controls reference, see API Debugger.

Testing a Module

Use the Internal tab to send a request directly to a module's API endpoint and inspect the execution.

1. In the Dev Overlay Toolbar at the bottom left of the Module Builder, select Debugger from the tool selector and expand the toolbar.

2. Select the Internal tab.

3. Use   Browse all routes or the Search APIs field to find the module endpoint to test. The HTTP method and URL populate automatically.

4. Optionally expand Execute Options to configure how the execution runs. See Execute Options below.

5. Configure the request body, headers, and parameters using the request configuration tabs.

6. Click Execute.

7. Review the results in the result tabs that display at the bottom of the panel.

Execute Options

Execute Options control how the module processes the test request.

Interpreting Results

After the execution completes, results display in tabs at the bottom of the panel. The result header displays the HTTP status code, response time, and a Clear button to reset the panel.

The Response tab displays for every endpoint. The following four tabs display only for the Execute Module and Execute via Proxy endpoints:

Use Group by step on the Event Log, Data Changes, and Timeline tabs to organize results by execution step. Select Collapse all to collapse all expanded entries.

Finding Slow Steps

Use the results to find where an execution spends its time.

1. Check the response time in the result header for the total duration of the request.

2. On the Timeline tab, look for the longest bars. Each step header displays its number of events and its duration, so the slowest step stands out. Hover over a bar to see the component, the event type, and the bar's offset and duration. For a component that runs asynchronously, the Execute bar covers the whole run, from beginning to end.

3. On the Event Log tab, check the time after each event, like +120ms. It is the time since the previous event. Gray means under 100 ms, yellow means 100 ms or more, and red means 500 ms or more. An event with a yellow or red time came after a long gap.

4. Select Group by step to compare steps. A step is one cycle of the execution engine. Components queued by triggers run in later steps, so a long chain of triggers produces many steps.