Add your first endpoint

Purpose

Map one request pattern to a local response and confirm matching behavior quickly.

Where this is used

All request-level behavior (mock response, passthrough, and disabled modes) comes from endpoints.

Setup prerequisites

• A running or stopped server exists.
• At least one collection or folder in endpoint tree (or create one).
• Decide whether you want local mock response or passthrough behavior.

Step-by-step

1. Select the server and open the endpoint tree.
2. Add endpoint in a collection/folder.
3. Set method and path, for example GET /health.
4. Set mode:
   • MOCK for local response.
   • PASSTHROUGH to forward upstream.
   • DISABLED to skip serving local response for this path.
5. Set status code and body for MOCK mode.
6. Save and send test request.

Expected result/output

• The request is matched via method + normalized path + query mode.
• Response appears in Live View with served-by status (`mock`, `passthrough`, or `strict_404`).
• Same-route variants (if any) remain mutually exclusive by active state.

Common issues + fixes

• Path does not match: verify path type and normalized path (`/users` equals `/users/`).
• Wrong query behavior: check `queryMode` when requests include query params.
• Mode seems ignored: confirm endpoint mode is active and route has no sibling conflict.

If routing is still uncertain, reviewRequest matchingand thenLive View.