An endpoint builder's canvas constantly checks the graph you're building and shows the result in a small badge, top left, right over the canvas: a block count, a connection count, and a green VALID or red N ISSUES pill. It updates the moment you add a block or change a connection, no button needed just to see whether something's wrong.
Getting the full list
Click Validate, in the builder's header, to open a panel listing every issue found, each one marked as an error (something that will actually break at request time) or a warning (probably not what you meant, but not fatal on its own). Clicking an issue that names a specific block selects that block on the canvas immediately, so you can jump straight to the problem instead of hunting for it.
What gets checked
- A Trigger exists and is connected. Every endpoint needs exactly one Trigger block, wired to the first real step.
- Every block is reachable. A block with no path back to the Trigger will never run, flagged as a warning so you notice it before wondering why it never fires.
- Every branch is wired. A Condition, Switch, Loop, Hash, Cache, Throttle, Health Check, or OIDC Login block has more than one named output, missing any one of them (e.g. Condition's "False" path, or a Switch case with nothing connected to it) is an error, since a real request could hit that exact branch and have nowhere to go.
- A block with several outgoing connections that isn't meant to branch. Warned as unusual, since normally only the branching blocks above should have more than one.
A few content checks
On top of the graph shape itself, a handful of block specific checks catch a likely mistake directly: a Response or Error Response block with an empty body (or an empty URL, in redirect or serve file mode), a Call External API block with no URL set, a Condition, Switch, or Assert block with nothing chosen to evaluate.
Tip: Validate doesn't block saving, an endpoint with real issues still saves fine, it's meant to catch a mistake early, not to gate your workflow.