When accessing an API endpoint that requires a header, requesting 'https://api.github.com/invalid' and calling raise_for_status() typically yields which status code?

When accessing an API endpoint that requires a header, requesting 'https://api.github.com/invalid' and calling raise_for_status() typically yields which status code?

• A. 200 - OK
• B. 404 - NOT FOUND
• C. 403 - FORBIDDEN
• D. 500 - SERVER ERROR

Answer: (B)

Understanding how HTTP status codes work is key here. When you make a request to a REST API and then call raise_for_status(), any 4xx or 5xx response will raise an HTTPError. The number after the status code tells you what happened with the request. In this case, the path you’re requesting doesn’t exist on the GitHub API: /invalid. That means the server has nothing at that URL to return, so it responds with 404 Not Found. The fact that a header might be required for other endpoints doesn’t change this outcome for a non-existent path—the resource isn’t found, so the server returns 404. Because 404 is a client error, raise_for_status() will raise an HTTPError for it. If you’re debugging, you’d see the exception tied to a 404 status, confirming the resource isn’t available at that URL. If you were hitting a valid endpoint but omitted a required header, you’d more likely see 401 Unauthorized or 403 Forbidden, but with an invalid path like this, 404 is the expected result.

Understanding how HTTP status codes work is key here. When you make a request to a REST API and then call raise_for_status(), any 4xx or 5xx response will raise an HTTPError. The number after the status code tells you what happened with the request.

In this case, the path you’re requesting doesn’t exist on the GitHub API: /invalid. That means the server has nothing at that URL to return, so it responds with 404 Not Found. The fact that a header might be required for other endpoints doesn’t change this outcome for a non-existent path—the resource isn’t found, so the server returns 404.

Because 404 is a client error, raise_for_status() will raise an HTTPError for it. If you’re debugging, you’d see the exception tied to a 404 status, confirming the resource isn’t available at that URL. If you were hitting a valid endpoint but omitted a required header, you’d more likely see 401 Unauthorized or 403 Forbidden, but with an invalid path like this, 404 is the expected result.