The Mirror Endpoint
Trace your http clients
Last updated
Trace your http clients
Last updated
Sometimes it is helpful to visualize what a http client sends to a web-server. If your client application runs on your local machine you could use network sniffers, or if the client runs in the browser, you could probably use plugins to visualize the messages sent. However, this is difficult to set-up and it won't work when the client application does not run on your local machine, for example, if it runs on any other machine on the web.
The Mirror endpoint responds what you sent to the service.
A Boomi Integration process runs on an ATOM, which is basically a JAVA web-service. There is no chance to visualize what goes out of the ATOM.
What you send to the Mirror endpoint it is responded, and it is temporarily saved (for one hour) under the , using your .
You can use the to visualize documents. Alternatively, you can request all mirrored documents querying the docs endpoint: GET /docs/query?Key=MSPro.Mirror&Context=*
This will return all recently mirrored documents from account SharedAccount: