Telerik blogs
FiddlerT3 Dark_1200x303

Ever use a third party API that seems to "randomly" fail on you? Learn how Fiddler Everywhere can jump in and help you to inspect and debug your network traffic.

For years Fiddler has been the gold-standard tool 🥇 for inspecting and debugging network issues for web, desktop, and mobile applications. Are you a React, Angular, Vue.js, UWP, Electron, NativeScript, React Native, Ionic, WinForms, ASP.NET, Ruby, (you get the picture) developer? Fiddler don't care! Fiddler is completely tech-agnostic. 

In this series, we are looking at a set of specific scenarios many of us regularly encounter during app development. Today we are going to look at that dreaded issue of remote APIs failing on us. These are remote resources that are completely out of our control, thus far more difficult to debug.

This is the final article in the series, so be sure to check out other articles:

NOTE: Have no fear! Fiddler Classic (the original Fiddler) isn't going anywhere! You can still download Fiddler Classic and use it like you always have on Windows.

So let's get started!

Our Scenario: Diagnosing a Failing Remote API

As a developer, I'm utilizing a remote third-party API for my app. While it had been working just fine for days, now every time I generate a request, it fails without any error context! I would just copy and paste the endpoint URL into my browser or another tool, but there are authentication tokens and parameters added to the request that make it a difficult request to generate manually.

Frankly I just need to quickly re-create the full request and inspect/debug the failed response, based on real world usage within my app.

Fiddler Everywhere's Solution

Using Fiddler Everywhere, we can easily view, record, play back, and inspect individual network requests made by any desktop apps running locally (including any modern web browser).

To diagnose and debug this particular issue we can:

  1. Open up Fiddler Everywhere and toggle the Live Traffic option to Capturing:


    fiddler everywhere capture traffic

  2. Open the app/website you are developing (be it a desktop or a web app). Navigate to where the failed request occurs and use whatever functionality necessary in the app to fire the remote request you are trying to debug.


  3. Back in Fiddler Everywhere, toggle the Live Traffic option to Paused so as to limit the flood of information coming in.


  4. Find the specific session you are interested in. In my case, I'll use the Host filter to only show traffic from a specific remote host, making it far easier to identify and work with the issue at hand:


    fiddler everywhere host filtering

  5. Look for the failed request out of all your captured sessions. (Hint: It'll likely be red if it's throwing an error.) When you find it, inspect the request—look for any improper parameters in the header or body of the request. You may also want to look for a malformed response.


    fiddler inspect request

  6. Next, load the session in Fiddler Everywhere's API Composer. Do this by right-clicking on the specific request and choose Edit in Composer.


    NOTE: This is far and away my favorite step. Why? Instead of just loading the URI into to the API Composer, Fiddler Everywhere also transposes any header values or other parameters to duplicate the request!

  7. In the API Composer, alter whatever possible header key/value pairs, parameters, or other mistakes you think you've found. Re-issue the request in the API Composer without going to a third party tool as many times as you'd like.


    fiddler api composer

  8. Assuming you've effectively re-created the issue, now is your opportunity to either fix the problem (if it exists in your app) or communicate the issue with the API owner. Maybe an opportunity for the collaboration features of Fiddler Everywhere? 😍



Today we took a quick look at how Fiddler Everywhere can be used to quickly diagnose and fix issues found when remote APIs fail.

What's next on your Fiddler journey?

Start your using Fiddler Everywhere by downloading a trial today for either macOS, Linux, or Windows. After that, read about an exciting new product in the Fiddler family: Fiddler Jam.

Happy Fiddling! 🎸

Rob Lauer is a Product Manager for Telerik
About the Author

Rob Lauer

A maker at heart and a supporter of the open web, Rob is Developer Relations Lead at Blues Wireless. You can find Rob rambling incoherently on Twitter @RobLauer.

Related Posts


Comments are disabled in preview mode.