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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. stop forced display of Request Headers

    Hello.
    When adding the "CONTENT TYPE" of Request Body's Representations in the publisher portal, Request Headers is forcibly displayed as "Content-Type (optional)" on the developer portal, so it is in a state that it can not be deleted or edited.
    I want you to stop forced display of Request Headers or make it editable.
    Thank you.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support System.Net.WebUtility in policies

    I have APIs that are returning json with properties that have html-encoded values, returning html encoded string in json isn't needed as the original service was based on xml and didn't use the CDATA tag. To be able to properly compose this API usage of an HtmlDecode function is needed which is readily available in System.Net.WebUtility

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Policies  ·  Flag idea as inappropriate…  ·  Admin →
  3. Is there any way to add new forms fields in subscription for approval

    Is there any options for adding custom field in subscription request form.

    So that we can request additional information for approval.

    Fields like:

    Subject:
    desciption:
    List params of in the product:

    For reference attaching screenshot.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API management experience  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add interface in API management service to show the backend service

    Add interface in API management service to show the backend service, could only access it via rest API at present(https://docs.microsoft.com/en-us/rest/api/apimanagement/backend/listbyservice)

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API management experience  ·  Flag idea as inappropriate…  ·  Admin →
  5. Git password generation should be URL encoded

    As it stands today, you have to URL encode the password before it can be used within Git. Note ampersand in partial password shown below.

    Partial Password -- 586ea4e36ccc210085030004&2017

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  API management experience  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow Server Side Events (SSE) to be consumed by client as text/event-stream and not as application/json

    We created a microservice using Spring WebFlux (will produce Server Side Events) to expose an API that will publish data as an event stream which is consumed by the client as EventSource. However, the Azure API Gateway is preventing the data to be consumed as text/event-stream.

    A similar concern is seen here: https://community.apigee.com/questions/61225/apigee-to-create-a-reactive-rest-api-for-continuou.html

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Gateway  ·  Flag idea as inappropriate…  ·  Admin →
  7. Enhance transformation policies to support formats such as csv, xlsx, etc.

    It is common to be requested to export data from the API queries to a format that can be shared and easy readable by other non-tech people. So i would say it would be good to be able to enhance the transformation policies to transform from JSON to CSV or XLS/XLSX. Or at least provide an option to export results to these formats on the API Management querying experience.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API management experience  ·  Flag idea as inappropriate…  ·  Admin →
  8. Open Id Connect - add required scopes in Developer Portal

    Currently it is not possible to add required scopes (or any additional URL or body parameters) to authorize requests.
    I think it is possible for OAuth0 integration.
    It might be worthwhile to add such possibility.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
  9. Having the ability to

    Having the ability to see which ciphers are active within the APIM. At the moment you can disable 3DES in the Portal and 9 other ciphers using a PATCH/PUT command but you cannot see which ciphers are actually active anywhere.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  10. Ignore scheme differences in <redirect-content-urls />

    By default APIM matches on the scheme when using this policy. It would be nice to have an optional flag on this policy to ignore the scheme when redirecting backend URLs to the proxy.

    Via the backend, we may build a URL as "http://mybackend...&quot; - when this is surfaced via the api we'd want it redirected to the APIM proxy as "https://api.mycompany...". Currently, APIM won't fixup this response because the scheme on the link emitted from the backend doesn't match the scheme on the backend API base URL.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Policies  ·  Flag idea as inappropriate…  ·  Admin →
  11. Ability to turn off Try it Now feature in Developer Portal or hide the button

    We have a Sandbox environment that we want to link to the Try it Now feature in Developer Portal. Since our API creates, tenders, and tracks shipments, we do not want users to have the ability to actually do these things in production just to "try it out." We want to turn off the ability for users to "Try it Now" or else customize that button to hit our Sandbox environment. Coding out a bunch of mock responses is not feasible due to the number of errors/responses that could be returned based on what a user enters.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API management experience  ·  Flag idea as inappropriate…  ·  Admin →
  13. Create product tags on portal

    Tags are able to be added to a variety of API Management resources including service, apis, operations, and products. Tags can be added via ARM, REST, or the Azure portal for each of these resources. For products, tags can only be added via ARM or REST and users are unable to add them via the Azure portal.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API management experience  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add API endpoint to detach all tags from an API

    We've got a CICD pipeline to deploy/update APIs using the API Management API. Currently we can only add tags as replacing tags would require querying for all API tags and then call DELETE for each tag.

    Please add an operation to support this:

    DELETE https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/apis/{apiId}/tags

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  API management experience  ·  Flag idea as inappropriate…  ·  Admin →
  15. Working with Policies in Ibiza

    Hi all,

    here are few recommendations related to user experience when working with policy editor in Ibiza.


    1. Click on 'Save' should save but not close policy editor. How about additional Save and Close button?


    2. FrontEnd blade of an operation should not be empty. It could show all required parameters for operation. Right now, we have to click Edit and see empty screen. Same issue for policies.



    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  API management experience  ·  Flag idea as inappropriate…  ·  Admin →
  16. Pre-populate Azure AD accounts to users with ARM template should act the same as the manual process

    I am pre-populating the users with Azure AD accounts with the following ARM template snippet using a VSTS CI-CD pipeline.

    {

    &quot;apiVersion&quot;: &quot;2018-06-01-preview&quot;,
    
    &quot;type&quot;: &quot;Microsoft.ApiManagement/service/users&quot;,
    &quot;name&quot;: &quot;[concat(parameters(&#39;serviceName&#39;), &#39;/&#39;, &#39;apim-dev&#39;)]&quot;,
    &quot;properties&quot;: {
    &quot;state&quot;: &quot;active&quot;,
    &quot;note&quot;: &quot;Application account for the SIAM application&quot;,
    &quot;email&quot;: &quot;<a rel="nofollow noreferrer" href="mailto:apim-dev@contoso.onmicrosoft.com">apim-dev@contoso.onmicrosoft.com</a>&quot;,
    &quot;firstName&quot;: &quot;Dev&quot;,
    &quot;lastName&quot;: &quot;User&quot;,
    &quot;identities&quot;: [
    {
    &quot;provider&quot;: &quot;Aad&quot;,
    &quot;id&quot;: &quot;12ca3158-2a1b-4a00-87dc-454ebaa5d238&quot;
    }
    ]
    }

    }

    When I run this template the user is added with authentication type Azure AD and Basic. I only want Azure AD as authentication type which should be the same behavior as if the user is sigin-in for the first time…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  17. Improve terminology (subscription, key)

    It's confusing that, for example, the rate-limit and quota policies have variations that are "by subscription" or "by key", when a "key" is also a crucial part of the subscription, but unrelated to the keys or values you can use to limit use.
    Subscription itself is also a confusing term vs the Azure subscription.
    I might suggest "registration" or "access key" for the APIM subscription, and the policies that limit by a "key" might just be called "by value" instead.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API management experience  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add support for configuring SSL settings of APIM instance using Git repo or Powershell

    We're trying to automate our deployment of APIM using the APIM git repositories. However, APIM currently doesn't support configuration for SSL settings of an APIM instance either using a git repository or Azure PowerShell cmdlets. We would like to have that support so that we can manage APIM completely through the git repository and powershell instead of having to change things in the Portal.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  19. Configure notifications programmatically

    We are populating and configuring our APIs using the REST API ( https://msdn.microsoft.com/en-us/library/azure/dn776326.aspx ), but there are a few settings that cannot be done programmatically and must be done by clicking into the portal.

    One of these settings is for the email notifications that are sent upon subscription requests, new subscriptions, etc. ( https://azure.microsoft.com/en-us/documentation/articles/api-management-howto-configure-notifications/#publisher-notifications ). We would like to be able to configure these programmatically, either via the REST API or some other way.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API management experience  ·  Flag idea as inappropriate…  ·  Admin →
  20. Enhance Json Serialization support in Policy Expressions for Legacy Backend APIs

    Provide access to JsonConverter types, e.g. JavaScriptDateTimeConverter so that a JObject can be formatted as needed for a legacy system.

    Currently, if a Json object needs to be translated to a different format for a DateTime property it is not easily possible to convert the APIM body JObject to what the backend service expected for Json serialization.

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

Feedback and Knowledge Base