Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I guess this is relative to API’s best practices. I am looking at implementing API and not really sure if I need to use views in API design or leave them for user’s frontend implementation. I don’t think is a good idea to implement views in API, but it would be nice to know what usually is done. I think API calls should always return either JSON or XML; adding views complicates everything…
Do you use views in APIs, yes/no, why?
API stands for Application Programming Interface. It is something exposed by your app that can be called to interact with it. REST is a philosophy which does not tell you how to design your application, just defines a communication structure (resources, representations, verbs, nouns).
A view is not a concept in REST, but in the most common case, a view will be a representation of a resource in REST. Although this view representation can be directly returned by the server, most developer prefer to return only the data and separate the visualization.
If your API returns HTML, that would not violate REST, but it would introduce coupling between the user interface and data of your application. I recommend that you don’t do it, not because of REST, but because you’d violate basic software design principles.