API Management

Microsoft Azure API Management is a turnkey solution for publishing APIs to external and internal consumers. Quickly create consistent and modern API gateways for existing backend services hosted anywhere, secure and protect them from abuse and overuse, and gain insights into usage and health. Plus, automate and scale developer onboarding to help get your API program up and running in no time.

How can we improve Azure API Management?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

  1. Support webhooks for notifications

    All API Management notifications are currently done via email.
    It would be great to add webhooks as a potential destination so we can automate certain process with services like Logic Apps.

    45 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    triaged  ·  1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

  2. Integrating Deployment Slot Hosted App Service to API Management

    In Azure, there are deployment slots within API App service as we have created it for Test, Stage, Preproduction, and Production. But in APIM, we couldn't select a specific deployment slot through hosted app service to Add APIs. Finally, we used Open API Specification.

    43 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

  3. Soap to Rest - Better error details

    Give better error description when the import process from WSDL to REST fails.
    At present time the error is quite generic and only give us the last xml node processed with success, leaving us to a painful try and error approach to why the import did not work.
    It would be nice to have more detail about the error, for instance the line number in the WSDL, the type of error detected (recursion,etc).

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

API Management

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice