REST isn’t my personal favorite, partly because I really don’t want to put things in a URL-string that is so easily manipulated ... unless it actually makes sense (and is possible) for the user to reasonably specify a RESTful URL-string entirely on his own.   (Or when it is both meaningful and harmless for me to build clickable hyperlinks.)   Otherwise, I tend to define a single /api entry-point and to use JSON in both directions.   The API simply implements a remote-procedure-call type of interface, and the URL-string means nothing.

A good example where REST might make perfect sense is in, say, a list of songs on a music site.   In that case, a URL-string of /song/nnnn, where nnnn is a song-number, might be just what the doc ordered.   But if it is strictly meant to be a program-to-program interface, I don’t ordinarily choose that route.