2 ms·

Can you elaborate. What kind of API? Just a HTTP/JSON api?

• ChrisMarshallNY 6y ago
  I prefer a REST-like API, like Google uses for their services (basically, sending is done with "raw" GET/POST/PUT arguments, instead of blocks of JSON/XML), and Raw/JSON/XML responses. But realistically, some levels of functionality are so intense, you need a “beefier” API, like GraphQL. If that is the case, it might not be a bad idea to review the API. In my opinion, overcomplicated APIs are likely to be the result of the service, trying to exert too much control over the interaction/presentation. Many times, an API is a "back window" or partial view to a more ambitious effort. For example, if the project is a Web-based framework, it will have a lot of rendering and View/Controller functionality that may be of no interest to something like a specialized text editor for content maintenance, so there would be no reason to expose that functionality. It may be a good idea to provide a suite of APIs, as opposed to a single one.