How can we improve Azure API Management?

Support additional filters on the GET /subscriptions endpoint

Currently, the GET /subscriptions endpoint in the Management API doesn't support OData filtering on the primary/secondary subscription key. This would make a nice enhancement.

For example:

https://myservice.management.azure-api.net/subscriptions?api-version=2014-02-14-preview&$filter=primaryKey eq '12345'

Current documentation for this endpoint:
https://docs.microsoft.com/en-us/rest/api/apimanagement/subscriptions#Subscriptions_ListByService

1 vote
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Ben Lambert shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
An error occurred while saving the comment
  • Ben Lambert commented  ·   ·  Flag as inappropriate

    Sure - at the time, I was trying to "upgrade" a given subscription to a higher "tier" (APIM Product) by issuing a PATCH request to change the ProductID on the subscription to a different product.

    Changing the ProductID is preferred (vs deleting and re-adding a subscription) because it preserves the subscription key values (and our internal history of calls).

    I had the subscription key but didn't know the subscription ID, so it would have been handy to filter the results of the GET /subscriptions request using the above OData syntax (since I had the key). The end result was to obtain the subscription ID so I could PATCH the subscription itself.

    Hope that makes sense, let me know if you need more info...
    thanks!

Feedback and Knowledge Base