Expose Office API via Swagger.
OK this is a radical idea from listening to @mkristensen talk about VS.NET tooling and how they are looking at supporting Swagger 2.0 to provide code generation for RESTful APIs in VSNET.
I looked up Swagger and their online documentation editor, and browser and here's an example
Which is surprisingly similar to Office 365's
I think Office 365 documentation on MSDN should still be the primary resource. Any future tie in to API-Sandbox would be awesome.
But if VSNET starts to support auto-codegen (like the old days with WSDL/Soap Services) from Swagger documentation, then I can also see having Swagger documentation is extremely useful.
Again, please refer to example for the idea and the podcast about what VSNET is thinking.
We currently have our open API (Swagger) descriptions available on https://github.com/microsoftgraph/microsoft-graph-openapi
We are working on having these available live on graph.microsoft.com API itself like $metadata. ^JT
Michael Buckingham commented
This would make Graph easily accessible from Flow and PowerApps.
Micah Rairdon commented
Yes, this would allow the endpoints to be instantly useful as we could auto-generate client-side libraries in any language we prefer to connect with (see swaggercodegen project).
This should be relatively simple considering you have OData everywhere and Oasis already maintains an xsl for conversion of metadata xml to Open API / swagger.json spec:
Jonathan McIntire commented
This would be completely awesome!
YES, this would be great and make development much easier. Just integrate the swagger file and VS generates the codes
John Liu commented
Swagger main site: http://swagger.io/