Skip to main content

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. If you look at the below screenshot you'll notice a small equal sign in the top right corner =.

partial request payload matching is enabled

partial request payload matching is disabled

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, then toggle the = 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" }
}


Was this page helpful?