As others have said, if we have to change the URL or headers in the request, we are not testing the code that will be deployed.
Its a real shame that the algorithm does not parse the POST params and find the closest matching example to respond with.
So close but so far 
I’ve been holding my breath for three years now, and I’m turning blue. Seriously, is this something we can realistically expect to happen ever?
I want to return “200 OK” if a header is set to specific value, and “401 Unauthorized” if the value is something else.
It does not seem to really work anymore, if it has ever worked. It seems to work only for one query parameter, but not at all if there are multiple query parameters.
Let’s assume we have two different example responses with exactly the same endpoint but with different values for query parameters, one example for query parameters ?param1=1¶m2=2 and another for ?param1=foo¶m2=bar, and we send a request with parameters ?params1=1¶m2=2. Now, the response depends on the creation order of those examples, and not at all the parameters or their values. The latest created example that matches the endpoint (without the query parameters) will be always returned, even when the query parameters and their values would match exactly.
In my example, the response stored to response example with query parameters ?param1=foo¶m2=bar will be given as the response to request with parameters ?param1=1¶m2=2, if that example was created after the response example with exactly the same query parameters my request had (?param1=1¶m2=2). Do you already have a bug report open about that or should I create it somehow?
Seriously people, We need this feature.