Set breakpoint conditions#

A breakpoint uses the same condition builder as rules and scripts. The conditions decide which requests trigger the pause.

Combine conditions with AND or OR#

The top of the Conditions section shows a Match label with two toggle buttons: AND and OR.

• AND: every row must match.
• OR: one row is sufficient.

The + icon adds another condition row to the group. The folder-with-plus icon adds a nested group. With nested groups you can build expressions such as (A and B) or (C and D).

Which fields the pause point allows#

The breakpoint's pause point controls which fields the dropdown offers.

Always available (request side):

• URL, Method, Host, Path.
• Request Body.
• Request Header..., Request Cookie..., Query Parameter....

Added when the pause point is After Response or Both:

• Status Code, Status Text.
• Response Body.
• Response Header..., Response Cookie....

For header, cookie, and query-parameter fields, an extra input lets you specify the name, for example the specific header to read.

Choose a comparator#

• contains, equals, starts with, ends with.
• matches (regex) for regular-expression matching.
• > and < for numeric comparisons, most useful with Status Code.

Edit a value in the code editor#

For body fields, regex patterns, and cookie values, a small </> icon appears next to the value. Select it to open a draggable editor. The editor highlights Text, JSON, XML, HTML, JavaScript, and CSS. When you select a structured language, the editor reformats the current value, so a minified JSON snippet becomes readable in one click.