Time to put everything together. You're going to inspect real API calls on the Banking Portal using your browser's Developer Tools. This is how senior testers debug issues in production — they open DevTools and watch the APIs.
Open the Banking Portal using the Practice link below
Open Developer Tools — press F12 (Windows) or Cmd+Option+I (Mac)
Click the "Network" tab at the top
Click "Fetch/XHR" filter to show only API calls (ignore images, CSS, etc.)
Now interact with the Banking Portal — log in, check balances, click around
Watch API calls appear in the Network tab as you interact
Click on any API call to see its details — Headers, Payload, Response
For each API call you see, write down these details:
API Call #1:
URL: ___
Method: GET / POST / PUT / DELETE
Status Code: ___
Request Headers: Content-Type = ___, Authorization = ___
Request Body: (if POST/PUT)
Response Body: (first 3 fields)
Response Time: ___ ms
API Call #2:
(same format)
API Call #3:
(same format)Open your terminal and run these commands. After each one, identify the status code, the number of items returned, and one field from the response.
Save your exercise answers. When you reach the Postman chapter, you'll repeat these same calls in Postman — and you'll appreciate how much easier it is compared to curl.
Key Point: DevTools Network tab is your X-ray vision into any web app's API calls. Use it daily.