REST API Design Guidelines Published

Currently, Microsoft published its “REST API Design Guidelines” for the API community. These guidelines goes on to represent a multi-year, cross-company, collaborative process combining the co-operative experience of the numerous engineers designing, operating and running the global scale Cloud Services across Microsoft and at the same time, also listening to the feedback on APIs from its partners and customers. The company has gone on to make an effort in order to incorporate those learning alongside the industry best practices in the API space to create the guidelines, which the entire API teams across Microsoft uses every day.
 
Microsoft states,
 
“The Microsoft REST API Guidelines, as a design principle, encourages application developers to have resources accessible to them via a RESTful HTTP interface. To provide the smoothest possible experience for developers on platforms following the Microsoft REST API Guidelines, REST APIs SHOULD follow consistent design guidelines to make using them easy and intuitive.”
 
They also stated,
 
“We recognize that in API design, there are multiple correct ways to do things (ex: snake-case vs. train_case vs. UpperPascalCase vs. …) and we are sharing these design guidelines as what we have settled-upon after much debate among Microsoft colleagues. We expect that these guidelines will evolve over time and that your feedback will play a part in that evolution.”