Azure-rest-api-specs: need a swagger for Azure Billing REST API

Created on 11 Nov 2015  Â·  7Comments  Â·  Source: Azure/azure-rest-api-specs

Being that we spend many thousands of dollars on Azure each month, we are interested in producing custom reports of the usage. I would like to use the relatively new Azure Billing REST API for this. I am looking for a Swagger definition of these APIs. I could probably help fill them out if the stubs get created in a git branch.

Most helpful comment

I have generated the swagger spec from the hyak spec in master branch and am currently reviewing it. So far the generated swagger spec looks good to me. If you want I can do a PR and everyone can review it. What does everyone think about it?

All 7 comments

+1

@Matt-Westphal could you comment on a timeline for creating a swagger representation of the commerce API?

Customers in node sdk have been requesting it as well https://github.com/Azure/azure-sdk-for-node/issues/1717

Hot topic in Python too, I received an email for this in December 2015.

@moinak3 might have a better answer for this.

I have generated the swagger spec from the hyak spec in master branch and am currently reviewing it. So far the generated swagger spec looks good to me. If you want I can do a PR and everyone can review it. What does everyone think about it?

Thanks Amar.

From: Amar Zavery [mailto:[email protected]]
Sent: Thursday, April 21, 2016 1:30 PM
To: Azure/azure-rest-api-specs [email protected]
Cc: Matt Westphal Matt.[email protected]; Mention [email protected]
Subject: Re: [Azure/azure-rest-api-specs] need a swagger for Azure Billing REST API (#57)

I have generated the swagger spec from the hyak spec in master branch and am currently reviewing it. So far the generated swagger spec looks good to me. If you want I can do a PR and everyone can review it. What does everyone think about it?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/Azure/azure-rest-api-specs/issues/57#issuecomment-213101736

Was this page helpful?
0 / 5 - 0 ratings