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.
Current documentation for this endpoint:
Hi Ben, would you mind explaining the use case behind this request?
Ben Lambert commented
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...