Should a response of api return instruction tell client how they should act? [closed]
Closed 1 hour ago.
Should a response of api return instruction tell client how they should act? [closed]
Closed 1 hour ago.
Should a response of api return instruction tell client how they should act? [closed]
Closed 1 hour ago.
Should a response of api return instruction tell client how they should act? [closed]
Closed 1 hour ago.
One or many RESTful APIs for large company?
I work for a large company which has several non-RESTful APIs. I am tasked with building a web application to interact with these APIs. Each API handles and provides very different business processes and data.
How do I assess tradeoff between robustness and “lazy” code in API design?
Postel’s law:
Data service API design
We’re designing a data service that will store a large number of statistics about stocks, including historical data. The client will be a web application, which will need to pull various bits of data to show in different places on the site.
How To Handle Login For An Unofficial API?
I am building a tool to access some data on a site (Fitocracy) and I would like to turn it into an unofficial partial API, as no official API exists.
When designing an enterprise API, what level is appropriate for separating libraries?
Assume we are developing a REST system for an enterprise company to expose the companies resources in a Java based application. Ultimately you have one web application, and domain libraries. My question is to where components and services should live in these domain libraries and what should exist in the application itself.
Should I use both WCF and ASP.NET Web API
We already have a WCF API with basichttpbinding.
Some of the calls have complex objects in both the response and request.