This is an excellent example of how the word "REST" in its common use tells you absolutely nothing about an API. This API certainly does not look like a Fielding-REST-API, and it doesn't even look like a programming-blog-REST-API (in my experience, bloggers just like to use "REST" to mean "HTTP + JSON + no RPC").

Why can't we just call this an "HTTP API"?