Partial request payload matching

note

This functionality is only available on paid plans. Check our plans here.

This is a super powerful hidden gem in our UI that can easily go unnoticed. Open the Request payload tab and look at the right hand end of the editor toolbar: the last button toggles between exact and partial matching. The caption under the editor always spells out which one is active.

Exact matching, the default.

Partial matching.

default behavior

By default, partial request payload matching is disabled. Hence, if the payload is not strictly equal to the request payload, no request is intercepted.

If you want to intercept a request based on a subset of the attributes of the payload, toggle that button to enable partial request matching.

For example, looking at the anatomy of a GraphQL request, the operationName varies from query to query. With partial request matching you can configure two different rules to intercept the same GraphQL request.

Here is a practical example with the following request payload:

{
  "operationName": "getCity"
}

tweak will match the following requests:

{
  "operationName": "getCity",
  "variables": { "id": "100" }
}

{
  "operationName": "getCity",
  "variables": { "id": "345" }
}

To learn more about how to work with GraphQL check this page.

---

Was this page helpful?

Need something else? Request a feature

  Thanks for your feedback!