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 for parameters in API prefix

    Let's say I have root like api.com/trees/{tree-name}. I'd like to have an ability to create Branches API with api.com/trees/{tree-name}/branches/. The only option right now is to keep tree-name in a query.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Josh Twist responded

    Hi Dmitry, thanks for providing this feedback. Can you help me understand why you’d like this additional feature? Be great to understand why this would improve the product for you.

  2. Support for OpenAPI extensions for generated specifications

    Customer would like to add a number of custom attributes to their swagger, but it needs to happen for all generated swagger out of APIM.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  3. Import Private API's

    You cannot currently import API's from a private URL on a virtual network.

    It appears to be a requirement that to import an API it must be on a public URL

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow SOAP services with complex WSDL to be manually built

    My organization has a large number of legacy SOAP services that have large complex WSDL based on external XSDs. Currently the APIM product is not able to manage the service operations given the complexity. Allow for the type structures to be manually created so that the management tools can function.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  5. Basic Support for WS-Addressing

    The current support for SOAP-based services is good enough for some scenarios. However, one that I see missing that would make integrating WCF-based services easier would be to support basic WS-Addressing.

    In particular, if the API is implemented in WCF using WSHttpBinding with only transport security, it will be exactly the same as a regular BasicHttpBinding-based service with SOAP 1.2, except it will also require the WS-Addressing <To> and <Action> headers.

    For now, we've managed to make it work in SOAP-to-REST scenarios by manually inserting the WS-Addressing headers into the set-body template, but this can be very annoying for complex…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add support for apiblueprint in Api Management

    I think you should try to support apiblueprint.org format for API management specification beyond WSDL and Swagger.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  7. Enable entry of multiple examples for a given operation

    The portal only permits one example of a 200 OK response. I worked around this limitation by creating a larger JSON object consisting of an array of examples one property of which is the actual response.

    E.g.,

    [
    {
    "Example": 1,
    "Description": "No filters are applied. Consequently, there are more than 25 results",
    "RequestUrl": "https://apis.conmetwheelends.com/aftermarket/v2/details/summary/~/~",
    "Response": {
    "Status": "TOO_MANY_RESULTS",
    "Message": "Indicates that the request was successful (it was a valid). However, the response returned too many results. This may occur if the request is under-constrained based on current data. Please apply additional filters to further constrain the result…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  8. Choose whether subscription key is taken as a query param, header or both

    Instead of the default where the subscription key is taken as both a query param and a header, allow the API administrator to choose. Also enable them to change the description of the field in the API definition.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  9. Swagger/WADL custom schema extensions for definition downloads

    We would like Swagger and WDL definitions downloaded from our Dev Portal to include a copyright notice. We could put text in the operation definition, but we'd rather have something formally in the swagger definition, preferably that was always present without relying on colleagues to place text in a form they fill out when adding new operations.

    For the Swagger, I could use the Info Object: http://swagger.io/specification/#infoObject

    and then have an x- extension always show up for each existing and future operation.

    For WADL, a custom namespace for extension.

    Most importantly, we need a way to inject something custom into…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add support for optional "format" property to Open API import and export

    API Management supports the Type parameter property and standard JSON types as its values but doesn't support the optional modifier Format property - Format property translates to a description and doesn't round trip on export. Format property is used by some code generators and it's important to have it represented in the model and supported in OpenAPI import and export.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  11. 2nd Import and Append of swagge docs loses definitions

    When I import XY swagger (Open Api 2) into Api Manager, the model definitions are there and all looks great. Now i am to import a different AB swagger (different api), it imports, but loses model definitions in the process, big issue if we want to use NSwag or generators

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  12. Consumption Plan DevOps

    Currently consumption plan services are not discoverable via resource explorer this will impact the ability to automate the deployment of apis between API Management instances

    This is important if the consumption plan is to be used a lead into higher level SKUs especially as there is no upgrade option from consumption to higher level skus.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow Api management publisher portal to host/upload root certificate to retrieve swagger document from web apis using self-signed certs

    Allow Api management publisher portal to host/upload root certificate to retrieve swagger document from web apis using self-signed certs.

    At the moment if you want to update the API's from a Web role using self-signed certs, it just fails to retrieve because of CA hierarchy or rather lack of.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  14. Import API to new revision

    Currently you can import a OpenAPI specification to either a new API, replace the existing API or append it to the existing API.
    It'd be useful to be able to create new revision off the newly imported rather then the currently available options.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  15. Display imported request body/response representations in the administrator portal

    When importing an API from Swagger (and possibly also other sources) the request body/response representations are visible in the developer portal, but not in the administrator portal.
    In the admin portal all representations are present, but empty.

    This is
    1. Very confusing as it looks like something went wrong with the import, since none of the example data seems to be present, and the schema info is also missing
    2. Very inconvenient when one wants to make changes to the example data/schema documentation (e.g. adjust indentation to improve display in the developer console).

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  16. Mock SOAP response

    Hello,

    there is a pity that APIM does not allow to easy mock SOAP based APIs. I mean that I will not use 'manually' policy set-body and edition via policy editor but use only GUI and eg. click on button/link and APIM generate set-body alone.

    It will help me a lot (a large set of modules and right now think about migration behind api gateway) ... and I think it is very usefull for all universe soap-based guys :).

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  17. Richer import for azure functions

    At the moment when importing an azure function limited metadata about the operation is captured in to the swagger.

    It would be useful if the import process could interrogate the use of attributes such as ProducesResponseType, Produces, Consumes etc.. to correctly generate the operation definition with models, content types etc..

    This could be rich enough to allow enums to be annotated with x-ms-enum, even if it required special APIM attributes to be used.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    need-feedback  ·  0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  18. Create apim vendor extension for swagger to import rewriteURL.

    If APIM could import a swagger with an x-msapim-rewriteurl extension key on the operation, I could then provide something like and OData endpoint for GET /MyResource({Id}) as GET /MyResource/{Id}

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  19. Documentation Per Group/Product/Policy

    Provide a way to specify the API documentation if a specific product is being used or based on the policy that applies to the API.

    If behavior changes based on a product, policy, or group this would let users affected by those changes to see the documentation associated to them instead of saying if you are XYZ then this will be required/returned.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  20. support template parameters in the version id

    support template parameters in the version id.

    We should support template parameters in versionId so that APIM API url doesn't have to end with version name every time.

    For example, the usage URL can look like http://harryapimanagement.azure-api.net/api/v1.0/content instead of http://harryapimanagement.azure-api.net/api/content/v1.0

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

API Management

Feedback and Knowledge Base