Checks

The Assertions tab holds a request’s checks. Each row is a kind of check, its target, an operator and the value you expect; after a Send, it shows the result.

How values are compared

• Numbers are compared by value, so 1180 equals 1180.00.
• Objects are compared without regard to the order of their keys.
• A status check accepts a class such as 2xx.

JSON paths

Point a check at a body field with a JSON path: $.data.id, [*] for every item, .* for every field, and filters such as [?(@.status == "paid")] (with ==, !=, <, <=, > and >=) or [?(@.discount)] for items that have the field. When a path can match several values, exists passes if at least one is there; every other check must be true for all of them.

Generate from response

Generate from response writes checks from the last response. Ids, times and values that look like secrets only get an exists check. It writes at most 20.

Reading the result

A failed check says what was expected, what came back, and often why, for example: There is no “customer” in $.data, which is an object with id, status, total. A check you changed after the last Send shows “not run yet”.