AnsweredAssumed Answered

Why there are specific endpoints for some modules when there are generic endpoints like /<module>

Question asked by Venkat Malli on Aug 19, 2016
Latest reply on Sep 14, 2016 by Jeff Bickart

Hi Experts,


In the API documentation for endpoints, we see around 68 endpoints which are not specific to any module(like /<module> GET, /<module> PUT and so on...). At the same time, we also can see GET and POST specific to certain modules like /Users, /Leads,  /Employees, /Calls, /Contacts and some others...


So, we can either use generic endpoint like "/<module> GET" for 'Employees' module or use "/Employees GET" to get the same response. Similarly for POST as well.


Can someone throw light on why there are specific endpoints for some modules inspite of having generic endpoints for the same operation like GET, POST?