Last post Sep 26, 2016 05:17 PM by Dmitry Sikorsky
Sep 26, 2016 03:03 PM|CoreAPIDev|LINK
What is considered best practices for creating web api(s)?
e.g http://<servername>:<port>/api/<version>/Customers, http://<servername>:<same port as cusomters>/api/<version>/orders
e.g http://<servername>:<port>/api/<version>/Customers, http://<servername>:<different port than
All the web api(s) are for same application and no one else will use these web api(s).
what are the pros and cons of each as well?
Sep 26, 2016 05:17 PM|Dmitry Sikorsky|LINK
Why you want to have different port for different entities? Or is it different APIs?
For one API (the set of urls and methods) I would suggest to have following urls:
I would suggest to add letter v as prefix of the version, not just 3, because 'v3' is very easy to understand even without any docs.
Also I think that default http/https ports is the best one because users of the API could just use it without specifying the port etc. And it could be
confusing for the new users that the port is not default one.
UPD: when developing something really big it could be good to have API separated from the general application (if you have one) using subdomain: