Paul Kirkpatrick

My feedback

  1. 649 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 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
    Paul Kirkpatrick commented  · 

    1) UI for a Portal Admin to Manage WebHooks exposed by the APIM Portal
    a) Create Name for WebHook Event
    b) Create Description for WebHook Event
    c) Enter URL for a Registration API (Actual API is something Portal Admin will need to make)
    i) When a Portal Developer registers/unregisters the APIM Portal will make this API call
    ii) API call payload will include data on the WebHook registered, Portal Developer,
    APIM Key, and Filter
    iii) This allows my custom application(s) to know who is registered
    iv) Bonus if I can just give APIM Portal a Queue and credentials and have it let me know that way instead
    d) Portal will auto-generate an API that the Portal Admin can invoke when the WebHook actually occurs
    i) Portal Admin will have code outside of APIM to invoke this when an Event occurs that matches
    the filter, and for the specific Portal Developer registered.
    ii) Above API will use the POST body as the event Payload
    iii) Bonus if I can instead have the Portal listen to a Service Bus/Storage Queue instead of this API
    iv) When this API is invoked, the APIM Portal will deliver the WebHook to the subscriber, built in re-try
    2) UI for a Portal Admin to associate WebHooks with Products
    i) Can Publish/Unpublish like API's
    3) UI for a Portal Developer to see WebHooks in Products they have access to
    4) UI for a Portal Developer to Manage WebHooks they subscribe to
    i) Can see what they have registered for
    ii) Maybe a way to test it? Not sure we need this
    5) API for a Portal Developer to register WebHooks (WebHook Publisher API)

    An error occurred while saving the comment
    Paul Kirkpatrick commented  · 

    Currently if I want to allow my information to be available through WebHooks I would have to stand up a new .Net Web Project, have a list of the events I support and so on.
    It would be amazing if API Management could be my WebHook handler. I could then manage access to the webhooks using subscription keys like I do API's. I could easily tie data for webhooks to my existing api's, add a policy on an API to publish out a webhook, etc.

    Paul Kirkpatrick supported this idea  · 
  2. 77 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  9 comments  ·  API Management » Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
    Paul Kirkpatrick supported this idea  · 
  3. 427 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  18 comments  ·  API Management » Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
    Paul Kirkpatrick supported this idea  · 
  4. 40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    triaged  ·  6 comments  ·  API Management » Service management  ·  Flag idea as inappropriate…  ·  Admin →
    Paul Kirkpatrick shared this idea  · 

Feedback and Knowledge Base