We're in a data-driven and Web API economy. Web API designers need to define what and how data should be exposed from a variety of apps, services, and stores. What are the challenges of unlocking your data and opening up access in a straightforward and standards-compliant manner? Is OData the right tool for the job? What does it mean from the point of view of designing an API?
An introduction to HATEOAS core principles, examples, and a look at the value of the approach for API providers and app developers.
The second of four episodes in the API Facade Pattern series: common patterns for an API facade.