Open jobinar opened 9 years ago
For Support plans offer type, there are 3 offers with durableId 0041P, 0042P and 0043P respectively. Depending on the durableId you specify, the OfferTerms in RateCard API varies. For offers like promotional offers there are 20 offer durableIds starting from 0070P, 0071P...0089P.
jobinar, What "subscription API" are you referring to which returns the OfferDurableId?
Here is the "Azure API Management REST API Subscription entity", and it does not return OfferDurableId, or any other field that contains the offer.
https://msdn.microsoft.com/en-us/library/azure/dn776325.aspx
@solvingJ : Probably I wasn't clear enough. I meant the subscription API provides the name of the subscription and we need the OfferDurableId
of this subscription. I wanted to check which OfferDurableId
should be used in case a subscription has multiple OfferDurableId
s
I notice there has been no movement on this issue.
Can Microsoft please identify how one should go to get the OfferDurableId for a subscription. You really don't want us firing the whole list from https://azure.microsoft.com/en-us/support/legal/offer-details/ until it suceeds to get this information.
In the meter card API:
https://management.azure.com/subscriptions/{subscription-Id}/providers/Microsoft.Commerce/RateCard?api-version={api-version}&$filter=OfferDurableId eq ’{OfferDurableId}’ and Currency lt ’{Currency}’ and Locale eq ’{Locale}’ and RegionInfo eq ’{RegionInfo}’’
it expects we provide the
OfferDurableId
whose name is obtained from the subscription API and the code is given here.However, some offers have comma-separated values. For eg. Support plans (0041P, 0042P, 0043P).
What value should be provided in the API for such offers? Or should the API be queried in an iterative fashion with each offer ID?