RESTful definition debates are endless, but here’s my two cents:
If your API lets clients interact with resources using standard HTTP methods *without* needing prior knowledge of endpoints (beyond the entry point), you’re golden.
HATEOAS is neat but rarely used outside academia or mega-complex systems.
For learning, MDN’s HTTP docs are solid. And yeah, your simple API sounds RESTful enough to me!
If your API lets clients interact with resources using standard HTTP methods *without* needing prior knowledge of endpoints (beyond the entry point), you’re golden.
HATEOAS is neat but rarely used outside academia or mega-complex systems.
For learning, MDN’s HTTP docs are solid. And yeah, your simple API sounds RESTful enough to me!
