JSON API seems like a great solution for building application frontends that need to communicate with their backend, and we’re in fact moving in this direction. Most agree this is a very good thing, but we’ve been debating the idea of switching our public API (used by third parties to integrate with our system) to using it as well. One concern is that since these third parties aren’t actually building apps on our API (their apps have their own internal API presumably) many of the sophisticated features of JSON API will actually just get in the way of folks trying to integrate us into their systems. Usually this involves copying data to/from the third party’s model to ours. For these types of consumers, an argument can be made that a simple JSON structure (even with more nesting) may actually be easier/better to consume.
Also, if anyone knows of any mainstream APIs using JSON API, I’d love see how they handle this.
I’d love to hear some different opinions on this, thanks!