How to include API version number v1, v2, v3, etc in the path (like .../v1/... ) and have it: being used to select proper version of Controller class carried over to Controller as a parameter (optional) HTTP Calls Here is how HTTP calls to different API versions would look like: /v1/User/SomeAction?param=zzz /v2/User/SomeAction?param=zzz .... /vNN/User/SomeAction?param=zzz Controllers Now let's take a look at the server side. In most

We have an Android App written in Java that performs HTTPS calls to our mobile API server running ASP.NET Web API 2 (C#). Some API methods require authentication, and some methods are "open". Protecting "open" methods is not required, but we still want to protect those "open" calls with digital signatures. So Android app will have a Private Key to sign the "open" API calls with. The strategy of delivering that private key into the app is irre