Exercise 6: Documenting Status Codes: Information From Developer Team
Exercise 6: Documenting Status Codes: Information From Developer Team
You should already have practice documenting request and response bodies from taking the
first course on JSON and XML. So this exercise will focus on documenting the HTTP status
codes, which show success or error.
Let's say that you are working for company that has a simple API, and the status codes returned
by every request can be described in one table. For this exercise, you'll be building that table.
• 200. Success.
• 401. The access token is not valid for this resource.
• 403. The number of API requests per month has been exceeded.
• 404. The resource name or ID is not valid.