Let's say the API is failing in the UI. What are the steps one, two, and three to debug the issue?

When an API call fails in the UI, a systematic approach helps isolate the problem. First, open the browser’s developer tools and go to the Network tab. Reproduce the error and inspect the request URL, headers, and payload. Verify that the endpoint is correct, the HTTP method matches the server contract, and any required authentication tokens are present. Second, check the response status code and body. A 4xx code indicates a client error (e.g., bad request, unauthorized), while a 5xx code points to a server issue. Look for error messages or stack traces in the response that can guide you. Third, examine the server logs or use a debugging proxy (e.g., Postman, Fiddler, or a backend logging service). Correlate the request timestamp with log entries to see how the server processed the call. If the server logs show an exception, trace the stack to the code path responsible. If the logs are silent, the request may never reach the server, suggesting a network or CORS issue. By following these steps—inspect the request, analyze the response, and review server logs—you can pinpoint whether the problem lies in the client, network, or backend.