---
title: "Comment by Oliver Ramstedt on \"REST API Design Best Practices\" | Hashnode"
description: "Great read! I'll have all new REST API devs read this before letting them loose haha. One change i would make though is regarding documentation. As this is a 'b"
url: "https://hashnode.com/posts/rest-api-design-best-practices/6781128c75418dcaadd69096/comment/67a5c128d0fb02f75abf9133"
---

[Discussion](https://hashnode.com/posts/rest-api-design-best-practices/6781128c75418dcaadd69096)

Comment [REST API Design Best Practices](https://hashnode.com/posts/rest-api-design-best-practices/6781128c75418dcaadd69096)

[Oliver Ramstedt](https://hashnode.com/@oliverramstedt)

[Feb 7, 2025](https://hashnode.com/posts/rest-api-design-best-practices/6781128c75418dcaadd69096/comment/67a5c128d0fb02f75abf9133)

Great read! I'll have all new REST API devs read this before letting them loose haha.

One change i would make though is regarding documentation. As this is a 'best practice' guide i would not suggest OpenAPI specifically as there are many ways to document API's. I think the important lesson is to just document the endpoint in a way that makes sense in the dev environment.