Checking local service versus manufacturing customers

Question

In our company, we have many microservices and web clients that make up our SaaS (software as a service).

When changing the behavior of a particular service (usually written in C # WebApi). We would like to test the integration behavior with a client who makes calls to this service. Since the developer working on the C # service locally, I would prefer not to clone and create this particular web client (with local settings to point to the local server) to see how it interacts with changes to the local server. Ideally, I could go to the deployed version of the client (develop, rc, prod) and redirect the requests that the client sends to the deployed version of my service to my local server.

I tried using tools like requestly . However, this only leads to answer 307 and the following error:

XMLHttpRequest cannot load http: // localhost: 59517 / api / users . Response to pre-flight sign is invalid (redirection)

For now, we are checking the correct behavior on the server using the TDD module tests. There are times when it would be nice to be able to use an already deployed client to test the local server in order to better understand what might break integration tests during automatic assembly. Are there standard methods for conducting this kind of microservice tests that are not related to local building / configuring the web client?