>I see Craig's provided an answer. Basically WebApi simply responds to HTTP requests by sending .NET objects (which can be complex) back to the client - in your case a browser in which case converting them to JSon objects makes sense (WebApi can do that for you automatically.)
>
>Behind that you will need another layer on the server which will retrieve data from SQL and convert it to suitable objects and which will update the SQL DB from data returned by the browser where necessary. This is where Entity Framework shines - it can do all that work for you. If you don't want to use it then the approach we talked about earlier (or Rob's suggestion) can work. My experience is that EF is simple to set up if you are working against a stable DB structure - but can get hairy if the DB design itself is in a state of flux.
>
>On the client you can make calls to WebApi using XMLHttpRequest or, maybe better, use the angularjs $https service (or the higher level $resource service). The advantage of angularjs is that it can update the DOM automatically when data is received (basically acting as a MVC/MVVM type controller on the browser).
>
>If you want to give me an example DB table I could probably knock up a concrete example for you....

Sorry for throwing many questions at you. Somewhere in one of your posts you said that you build your pages in plain HTML (not ASP.NET or ASP MVC). But what technology have you used for creating your WebApi?