I've had a similar experience with REST over the years, and have come to a similar conclusion about just POSTing JSON as an API. I use the URL to specify which message is being sent (to verify permission with JWT, and to know how to deserialize), although that could just as easily be a JSON envelope.
I think to implement REST "properly" is a non-trivial amount of work, perhaps even a wild goose chase to iron out all the deficiencies. As a result, most everyone implements it "improperly" as CRUD because it's easy and familiar. But that turns into a huge mess over time.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've had a similar experience with REST over the years, and have come to a similar conclusion about just POSTing JSON as an API. I use the URL to specify which message is being sent (to verify permission with JWT, and to know how to deserialize), although that could just as easily be a JSON envelope.
I think to implement REST "properly" is a non-trivial amount of work, perhaps even a wild goose chase to iron out all the deficiencies. As a result, most everyone implements it "improperly" as CRUD because it's easy and familiar. But that turns into a huge mess over time.