Identify the request behind a page action
Find which endpoint the page calls and know where to inspect outgoing data.
Find which endpoint the page calls and know where to inspect outgoing data.
Before you begin
Section titled “Before you begin”- An open, running page in the HTML Editor that can generate the request you want to inspect.
Capture one action
Section titled “Capture one action”Open Network in Page Panels, clear the list, and trigger the page action once. Use XHR to narrow the list to data requests if necessary.
Identify the endpoint
Section titled “Identify the endpoint”Find the request by its filename and query string. Hover its label to see the full URL. Confirm the endpoint and parameters match the action you intended to call.
Check what this panel exposes
Section titled “Check what this panel exposes”Expand the entry to inspect response Status, MimeType and Headers, plus Body for a parsed JSON response. These are response details: this panel does not provide a separate Request section or a submitted-form payload view.
Inspect outgoing values when necessary
Section titled “Inspect outgoing values when necessary”For request method, request headers or the submitted payload, use the running page’s browser developer tools Network panel and reproduce the action. Compare input names and values with the Server Connect action inputs. An absent request points to the page trigger; a wrong payload points to the form or input bindings.
Check your result
Section titled “Check your result”You can distinguish a missing request, the wrong endpoint and the wrong submitted data.