reading-notes

Reading Journal

Understanding REST principles and HTTP verbage helps me better understand how web APIs function, making it easier for me to interact with them. Knowing how to structure URIs allows me to create accessible endpoints, improving the usability of my applications. Learning about HTTP status codes ensures I can understand server responses correctly, allowing me to handle errors and successes effectively in my code.

Reading

API Design Best Practices

1. What does REST stand for?

2. REST APIs are designed around a __.

3. What is an identifier of a resource? Give an example.

4. What are the most common HTTP verbs?

5. What should the URIs be based on?

6. Give an example of a good URI.

7. What does it mean to have a ‘chatty’ web API? Is this a good or a bad thing?

8. What status code does a successful GET request return?

9. What status code does an unsuccessful GET request return?

10. What status code does a successful POST request return?

11. What status code does a successful DELETE request return?

Things I want to know more about.

I want to know more about HTTP codes and how the history behind them. How they were decided upon to be the end all be all verbage that the entire world would end up using.