Skip to Content
DocsHandler Table

Handler Table

The handler table is a table that shows all the handlers in the project and control them.

Set Response Behavior

HTTP handler Behavior selector

Control how your mocked APIs respond using the behavior selector. Each handler can be configured with the following response types:

Available Behaviors

Tip: Use these behaviors to test how your application handles different API response scenarios.

Control

  • default

    • Executes the original handler logic you’ve defined
    • Uses your custom mock implementation

  • delay

    • Simulates an infinite loading state
    • Request remains pending indefinitely

  • return null

    • Responds with a null value
    • Useful for testing null handling

  • custom response

    • Uses the response saved in the Custom Response column
    • Save the response first, then select this behavior to apply it

Error

  • network error

    • Simulates network failure scenarios
    • Triggers error handling in your application

  • HTTP status codes

    • Select one of the supported status codes to simulate a client- or server-side response

The status behavior options are 400, 401, 403, 404, 405, 406, 409, 412, 413, 415, 429, 500, 502, 503, and 504. These are the HTTP status codes currently supported by the Dev Tool.

Mock Enable

Use the Mock Enable toggle in each HTTP row to pass requests for that handler through to the real endpoint. The behavior selector only controls the response while that handler is enabled, so switching it off does not discard its selected behavior or custom response.

Because a disabled mock is allowed to reach the configured backend, use a local or staging backend and non-sensitive data for this check.

The toolbar Mock Enable toggle is a global switch for both HTTP and WebSocket mocks. When it is off, all requests and WebSocket connections pass through and active mock WebSocket connections close. Individual HTTP, endpoint, listener, and logical event-branch settings are preserved, so turning the global switch back on restores their prior behavior.

Reset

Reset Dev Tool button

You can reset all handlers to their initial state using the Reset Dev Tool button:

  • All HTTP and WebSocket response behaviors will be set back to default
  • Global mocking and every HTTP/WebSocket enable toggle will be enabled for mocking
  • Temporary HTTP handlers, WebSocket endpoints, and WebSocket listeners will be removed
  • Active mocked WebSocket connections will be closed
Last updated on
WebSocketTools