- 1 Introduction
- 2 How to download Fiddler (it’s FREE)
- 3 How to start/stop Fiddler two ways – Capture HTTP(s) Traffic
- 4 How to capture HTTPS traffic in Fiddler
- 5 How to view Web Request and Response in Fiddler
- 6 How to Test API using Fiddler (Call REST API for without Postman)
- 7 How to view and format JSON / XML data in Fiddler
- 8 How to use fiddler Converters (e.g. Base64 / URL encode – decode)
- 9 How to add Request Start Time, Overall Elapsed Time Columns in Fiddler
- 10 How to edit and execute the processed requests in Fiddler
- 11 How to diff Fiddler requests
- 12 How to show SSIS PowerPack requests in Fiddler
- 13 View HTTP Request in Fiddler
- 14 View HTTP Response in Fiddler
- 15 View compressed (i.e. gzip, deflate) Response in Fiddler raw view
- 16 How to compare requests / re-execute
- 17 How to show web request of Curl in Fiddler
- 18 How to show SoapUI requests in Fiddler
- 19 How to show aws command line requests in Fiddler
- 20 How to show Windows Service requests in Fiddler (Local System Account)
- 21 REST API integration using ODBC in BI Apps (e.g. Power BI, Excel, Informatica, Access, C#…)
- 22 REST API integration in SSIS
Fiddler is one the most popular tool to inspect your Http Traffic. This tool helps you to test REST API / SOAP Web requests very easily. If you are using SSIS PowerPack or REST API ODBC Drivers you will find this post really useful to debug various REST API integration issues.
When you run Fiddler on your system, it acts as a tiny Web Proxy that sits between your client application and the webserver. Fiddler only starts capturing traffic when you running it. By default, it runs on the local machine (127.0.0.1) Port 8888. You can change the default port from Tools > Options.
How to download Fiddler (it’s FREE)
You can download Fiddler using this link for FREE (If that link doesn’t work then try this one)
Make sure that you have Downloaded the Fiddler Classic and not a Fiddler Everywhere.
It is not our product, this article is just to show you how you can analyze the API Request and Response call made from our Tasks/Components/Drivers.
How to start/stop Fiddler two ways – Capture HTTP(s) Traffic
After you install Fiddler, Go to Start Menu >Search for Fiddler
Launch Fiddler exe and it will start capturing HTTP traffic (For HTTPS URL see next section).
Run fiddler to start capturing web requests/responses made by various client applications on your system (e.g. Curl, Chrome, Internet Explorer). To start/stop capture go to File > Check/Uncheck [Capture Traffic] option.
By default when you run Fiddler it behaves like the default proxy server on your system. However, not all web requests appear in fiddler unless the client application using a system Default Proxy.
How to capture HTTPS traffic in Fiddler
By default Fiddler doesn’t show the content of Web requests made to HTTPS Url (Secure site) because it’s encrypted. Perform the following steps if you want to see HTTPS Traffic.
- Launch Fiddler
- Go to Tools > Telerik Fiddler Options > HTTPS > Check [Decrypt Https Traffic Option]
- Once prompted Accept certificate generated by Fiddler
How to view Web Request and Response in Fiddler
Once your web requests appear on the left side panel. Simply double click on the request entry to view. On your right side, you will see two panels.
- Top Panel – Request View
- Bottom Panel – Response View
Here is an example of seeing API calls generated by aws command line requests/response in Fiddler.
How to Test API using Fiddler (Call REST API for without Postman)
Fiddler comes with another cool feature just like Postman so you can test your API call. Basically, there will be a time when you like to edit your request and test with different data (e.g. URL / Body or Headers). If that’s the case you can directly go to Composer Tab or Replay existing request right Right Click.
How to replay existing request / edit / send new request
To reply to the existing request
How to view and format JSON / XML data in Fiddler
By default Fiddler will show you JSON / XML Tab if request body or response data in that format (see JSON / XML tabs on top and bottom panels). But what if you like to see in Raw Text but in Syntax Highlighted / formatted way?
How to use fiddler Converters (e.g. Base64 / URL encode – decode)
There will be a time when you like to encode / decode strings appearing in web requests. Fiddler has another very handy feature call Send to Text Wizard. This option appears in most right click Menu in Raw / Syntax View / Headers view and other places.
How to add Request Start Time, Overall Elapsed Time Columns in Fiddler
It’s really useful to see how much time each request is taking. For that, you can try the below steps in Fiddler Classic
- Right-click on any Header Column
- Select “Customize Columns”
- Choose “Session Timers“
- Choose Overall_Elaspsed and ClientConnectedTime from the dropdown
How to edit and execute the processed requests in Fiddler
If you want to re-execute existing requests in Fiddler with different parameters then try the below steps
- Select request from the left-hand side panel (or may be bottom side)
- Press “E” and you will see a panel like below
- Edit your request (i.e. URL, Header or Body)
- Click on Run to Complete
How to diff Fiddler requests
Sometimes you like to see difference between two requests. Fiddler comes with very handy feature. Just select two requests and click Diff Option in Right click menu. For diff to work make sure you install some diff utilities like KDiff3 or WinMerge.
How to show SSIS PowerPack requests in Fiddler
In most cases SSIS PowerPack requests will apperar in Fiddler without any extra configurations. However in some cases applications like SSIS PowerPack cannot detect it as System Default Proxy automatically. In that case try to enable Proxy settings in HTTP Connection or OAuth Connection. If you are not using connection manager then some Components like JSON Source offers its own Proxy tab so just check Enable Proxy.
By default Fiddler register itself as Default Web Proxy on port 8888 (i.e. http://127.0.0.1:8888 )
View HTTP Request in Fiddler
To inspect HTTP Web Request using Fiddler perform following steps.
- Click on the web request entry on left pane
- Click on the Inspector Tab > Click Raw from top panel
View HTTP Response in Fiddler
To inspect HTTP Web Response using Fiddler perform following steps.
- Click on the web request entry on left pane
- Click on the Inspector Tab > Click Raw from bottom panel
- You can also click on JSON or XML Tab if your want to see response coming in specific format
View compressed (i.e. gzip, deflate) Response in Fiddler raw view
When response is compressed then by default you wont be able to see it in Raw tab. When response is compressed you may see header like below in response headers. You can also click on
To view compressed response in fiddler perform following steps.
- Click on the web request entry on left pane
- Click on the Inspector Tab > Click Transformer tab from bottom panel
- Click on transformer tab and select No compression option and then click Raw tab
How to compare requests / re-execute
Sometimes you want to compare two requests and find the difference. Here is how you can compare requests and re-execute same request or edit it.
How to show web request of Curl in Fiddler
By default some application such as Curl doesn’t use system default Proxy. That means if you running Fiddler and trying to analyze requests made from Curl command line then it wont show up. Its easy to tell curl that which proxy server to use. Just use -x command line option with proxy server IP and Port (e.g. Default Fiddler IP and port … 127.0.0.1:8888 )
curl.exe -v -x 127.0.0.1:8888 https://google.com
How to show SoapUI requests in Fiddler
If you are using an application like SoapUI then also it may not use Fiddler as default web proxy. to show your SoapUI web requests in Fiddler try following options
How to show aws command line requests in Fiddler
If you are using aws command line application and want to show requests in Fiddler then add –no-verify-ssl like below. This way you can capture RAW API requests and use it like this in SSIS.
aws lambda invoke --function-name HelloWorld c:\temp\outputfile.txt --no-verify-ssl --payload file://c://test/customer.json
How to show Windows Service requests in Fiddler (Local System Account)
By default if Fiddler launched as Admin it will capture most of requests by various apps. But if your like to capture Web requests which are issued by windows service such as ZappySys Data Gateway then you might have to do little extra work (Assuming Service is not setup Run As Your account). By default many service Run under “Local System” account
Here is how to capture those requests which are issued by service account.
- Go to Folder where Service Exe is located (If you are unsure simply right click on Service > Properties and check path)
- Create new file in the same folder where Service Exe is located. File name must be <yourexename>.exe.config
- Enter following XML text in your config file and save
XHTML1234567<configuration><system.net><defaultProxy enabled="true"><proxy proxyaddress="http://127.0.0.1:8888" bypassonlocal="False"/></defaultProxy></system.net></configuration>
- Restart Service and check Fiddler now see requests are captured
REST API integration using ODBC in BI Apps (e.g. Power BI, Excel, Informatica, Access, C#…)
If you want to consume API data in SQL Server (without ETL) or Live API consumption in Tools like Power BI, Excel, Tableau, SSRS, Talend, Informatica then use ODBC PowerPack from here. See below table for each use case.
BI / Reporting Tools Integration
|ETL Tools Integration||Programming Languages Integration|
REST API integration in SSIS
If you use SSIS as your primary etl tool and you have API integration usecase then check this product.