# Read API behind UI Testing **URL:** \ **Category:** Bug Report\ **Tags:** web-testing, bugs-report, katalon-studio\ **Created:** [September 15, 2025, 10:24am UTC](https://forum.katalon.com/t/read-api-behind-ui-testing/182216 "2025-09-15T10:24:05Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![zedromason](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/zedromason/32/23869_2.png) [@zedromason](https://forum.katalon.com/u/zedromason)\ **Post date:** [September 15, 2025, 10:24am UTC](https://forum.katalon.com/t/read-api-behind-ui-testing/182216/1 "2025-09-15T10:24:05Z")
Is it possible to add API hits to the log while running a UI test? For example, after logging in, read which endpoints were hit, including the full endpoint name, type, method, and status. ---
**Author:** ![kazurayam](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/kazurayam/32/333_2.png) [@kazurayam](https://forum.katalon.com/u/kazurayam)\ **Post date:** [September 15, 2025, 10:33am UTC](https://forum.katalon.com/t/read-api-behind-ui-testing/182216/2 "2025-09-15T10:33:02Z")
I guess you want something like this: [http://forum.katalon.com/t/browsermob-proxy-in-katalon-studio-a-sample-project/83322](http://forum.katalon.com/t/browsermob-proxy-in-katalon-studio-a-sample-project/83322) ---
**Author:** ![kazurayam](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/kazurayam/32/333_2.png) [@kazurayam](https://forum.katalon.com/u/kazurayam)\ **Post date:** [September 15, 2025, 12:46pm UTC](https://forum.katalon.com/t/read-api-behind-ui-testing/182216/3 "2025-09-15T12:46:03Z")
> [@zedromason](#): > > read which endpoints were hit, including the full endpoint name, type, method, and status. If you want to monitor such Network events inside browser in a event-driven manner, Playwright is the tool you should use: See > **[Network | Playwright](https://playwright.dev/docs/network#network-events)** > > Introduction Also Puppeteer is nice for such advanced problem: > **[Network logging | Puppeteer](https://pptr.dev/guides/network-logging)** > > By default, Puppeteer listens for all network requests and responses and emits network events on the page. * * * Selenium 4, which runs inside Katalon Studio v10.x, supports “Chrome DevTools Protocol”. See > **[Chrome DevTools Network Features](https://www.selenium.dev/ja/documentation/webdriver/bidi/cdp/network/)** > > Network features using CDP. When I write a test using the native Selenium 4 Java API, I use IntelliJ IDEA. IDEA provides a complete support; it is a fun. But, how can I do the same in Katalon Studio? I don’t know. I would never go for Selenium CDP in Katalon. ---
**Author:** ![dineshh](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/dineshh/32/24488_2.png) [@dineshh](https://forum.katalon.com/u/dineshh)\ **Post date:** [September 16, 2025, 5:54am UTC](https://forum.katalon.com/t/read-api-behind-ui-testing/182216/4 "2025-09-16T05:54:46Z")
Selenium 4 supports Chrome DevTools Protocol CDP, which allows capturing network events..integrating CDP with Katalon Studio is advanced and can be technically challenging if Network Monitoring is priority, Alternate Tools like **Playwright** and **Cypress** have built-in support for monitoring and logging API calls directly during tests, enabling easier extraction of network data. ---
**Author:** ![kazurayam](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/kazurayam/32/333_2.png) [@kazurayam](https://forum.katalon.com/u/kazurayam)\ **Post date:** [September 23, 2025, 9:27am UTC](https://forum.katalon.com/t/read-api-behind-ui-testing/182216/5 "2025-09-23T09:27:49Z")
> [@dineshh](#): > > if Network Monitoring is priority, Alternate Tools like **Playwright** and **Cypress** have built-in support for … Previously, @Rob1 wrote his experience about Cypress: > [@Serious Recorder Bug - does not work with React](http://forum.katalon.com/t/serious-recorder-bug-does-not-work-with-react/143083/12): > > Ha, I tried that a couple of weeks ago. On paper, it looks like a great tool, but in practice it was unusable. The UI is ridiculously slow - so setting tests up is too painful to even try. I persisted for a bit and did get a simple test running (Just going to a log in page, logging in and navigating to somewhere in my app). The execution of the test was also way too slow. In Recorder, I have 1000s of lines of tests. At the speed Cypress executed tests, it would take days to complete testing, so… Once I tried Cypress as well. I gave up on it.