Sniffer, traffic analyzer or a proxy to use QA for testing api web apps?

There is a web app, when testing is needed to see what was sent it got in response. Plans security checks or no load, are now used purely dev Tools of browsers.
Inconvenient, as you have to upgrade and redo actions. Does it make sense to use any tool of the representatives above, or search through the recorded traffic might be too long?
And which tool is better?
March 19th 20 at 08:26
3 answers
March 19th 20 at 08:28
Postman everything! If the team is large you can buy
It can be configured as a proxy and intercept the messages? - laron.Hansen commented on March 19th 20 at 08:31
@laron.Hansen, no. It is for testing the API, not traffic. If you are going to analyze the traffic that specify the task - it depends on needs - Efrain commented on March 19th 20 at 08:34
March 19th 20 at 08:30
https://www.charlesproxy.com/
good stuff. You can watch the queries, the Soviets, to change the values in requests and responses
Well and when testing mobic
March 19th 20 at 08:32
Fiddler https://www.telerik.com/fiddler - analog charles, no pop-up advertising Windows
on Linux operating standards using mono

Find more questions by tags FiddlerCharles Web Debugging ProxyAPI