How to Design a Good Rest API

GraphQL like they have this really good separation where you basically can't have unintended side effects because you're either doing a query or you're doing a mutation at the same time. They kind of abuse the HTTP spec by saying everything is a post no matter what even the queries are posts so you lose you kind of lose that that safety guarantee at theHTTP level but you gain it back at the protocol level and I've seen more just like get user and then as part of the posts you have ID one in the body yeah of the post.