Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.


My feedback

  1. 680 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  API Management » Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →

    Hi all – we could really use more information on the use cases you would like us to deliver with this feature. To quote Darrel’s post below:

    Are you looking for some kind of UI in the portal to enable developers to subscribe to webhooks exposed by APIs?
    Or are you looking for the additional security provided API Management to limit what events a user can subscribe to?
    Do you want to correlate the API Management subscription ID with registered webhooks?
    Any information you can give about the scenarios you would like help with would be great.

    Many thanks

    An error occurred while saving the comment
    Jeff commented  · 

    Darrel, currently I would have to take different webhook nuget packages and host them in my api layer (ala web apps, web api or whatever else). I would like all those packages to simply be available in the api management and easily add new ones as they come in. So api management is now the single resource responsible for throttling my api and allowing a single point to integrate with other tools like wordpress, slack, tumblr, medium, whatever else. There is no reason for me to spin up api layers of my own just to host webhooks.

Feedback and Knowledge Base