A RESTful service is (usually as of today) a JSON API. They aren’t mutually exclusive things.
There’s no black and white definition there.
However, when someone is creating a RESTful service, they’re stating that they’ll be paying mind to HTTP Verbs and status codes as a fundamental part of their design.
In the original image posted, that dev clearly wasn’t paying mind to the HTTP layer and as such a commenter called it just a “JSON API”, which is the catchall, ugly, Wild West, typical way of doing things (always return 200, errors are in the json).
Once again tho, it’s not black and white. Others can and will disagree and want to be pedantic. I’ve been a professional dev for 35 years, devs love to argue abt this shit.
Look no further than Lightshot. It’s free, it can replace the PrntScn button. It lets you draw a rectangle, then add arrows, lines, text, then either copy to clipboard or save to disk.
Then it disappears. No unneeded prompts, no wasting your time, no ads, no upsells. Nothing. Lightweight, simple, and free. It’s like a throwback to the 90’s freeware.
As a software developer working with QA and often having to explain things to others as well, I’ve used this for years. It is the most optimal and efficient software for this purpose.