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. Deploy API management on-site

    We expost a number of developer API endpoints that are controlled via various API keys and products. We are looking to bring the functionality fully in-house and API management looks to fit the bill. Thus far it looks like there is only AZURE cloud... self-hosted would be ideal.

    686 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  2. Schema validation in APIM

    When an actual request comes, we need to validate the schema of the request and while sending back the respose, the schema should be validated. Similar to validate feature of API connect (IBM).

    http://www.ibm.com/support/knowledgecenter/SSFS6T/com.ibm.apic.toolkit.doc/rapim_ref_ootb_policyschemaval.html

    185 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  3. http2

    Enable http2 for the API Management

    48 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  4. Expose API Management Events

    Expose events from API Management.

    Example would be, a user registers. Currently we get an email. It would be nice if it was an event we could subscribe to (WebHook or API Call or Service Bus message.. etc) so that we could use the user registration as the start of a workflow.
    Another example would be if a user requests a Product, having an event we could leverage things like PowerApp/Flow/Logic App to start an approval process or setup their development environment.

    Simple Event list that would have the most value:
    -User Created
    -User Requested Subscription
    -Issue Created

    33 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  6 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  5. apim should allow more than 260 characters for URL path segments

    API definitions which have an ID as one path segment can have path segments which are larger than 260 characters (which is a windows limitation). Unfortunately this limitation is also part of the apim service and can be inceased by the product team on request. Why not setting it to a larger value as default or let me set an option like (windows compatible path length) when creating the instance?

    This problem is very critical if you face it because the apim service itself will block the request and you cannot handle/modify/forward the request to something else which can handle…

    18 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  6. Expose IntegrationModuleBitsVersion and IntegrationModuleVersion via ARM API

    I have noticed over time that when MS rolls out out an update to a tenant that properties in configuration.json may change: specifically IntegrationModuleBitsVersion and maybe IntegrationModuleVersion

    This is not exposed through the ARM API capabilities. Make the properties readable from ARM or even the legacy API or some other way that may be automated. I would like to check the values periodically and get a heads up to do wider regression testing when I detect a change there.

    18 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add support for IPV6

    Due to new Apple requirements (all apps must works over IPV6) we need to reach our Azure API Management through this protocol. Actually the AAAA is not present for any endpoint.

    12 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow CORS headers for Management API

    In order to invoke Management REST API endpoint (like ***.management.azure-api.net/apis?api-version=vvv) from browser's JS code, CORS headers should be enabled there. Moreover, full Management REST API endpoint configuration (thru Azure portal) is very welcomed addition.

    9 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  9. Option to disable or purge cache

    Option to disable or purge cache (by single API or entire service)

    9 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  10. Can we have anything built into APIM to ping backend or Alert when there are sporadic errors connecting to backend?

    Can we have anything built into APIM to ping backend or Alert when there are sporadic errors connecting to backend?

    This way i will either know when the backend is not reachable or when there are other issues connecting to the backend..

    6 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  11. A powershell script to enable application insights logs per API

    When an API is imported, it is possible to do so via powershell and apply several settings to that API. However, I would like to see that the settings regarding logging to application insights could also be managed via a powershell cmd.

    6 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  12. REST APIs through APIM backed by internal oData services

    We would like to provide REST APIs through APIM backed by internal oData services. The REST APIs will provide a subset of what the oData services provide. We would like to do this with no or minimal coding and we don't believe that this is possible today. We are requesting subsetting an oData service and lightweight transformations.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  13. Enable tracing in the Manager

    The trace capability is really useful but has to be enabled currently in the client by setting an additional HTTP header.

    If I have a production issue I can't amend code to do this and I may have many clients so would like to be able to turn this on in API Management with a simple checkbox or policy change at an API operation level

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support additional filters on the GET /subscriptions endpoint

    Currently, the GET /subscriptions endpoint in the Management API doesn't support OData filtering on the primary/secondary subscription key. This would make a nice enhancement.

    For example:

    https://myservice.management.azure-api.net/subscriptions?api-version=2014-02-14-preview&$filter=primaryKey eq '12345'

    Current documentation for this endpoint:
    https://docs.microsoft.com/en-us/rest/api/apimanagement/subscriptions#Subscriptions_ListByService

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  16. Use wildcard url in backend entity

    Could you support wildcard in the url of backend entity?

    Take following backend for example, we would like to use https://*.contoso.com/ instead of https://abc.contoso.com/.

    {
    "id": "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.ApiManagement/service/apimService1/backends/proxybackend",
    "type": "Microsoft.ApiManagement/service/backends",
    "name": "proxybackend",
    "properties": {
    "description": "description5308",
    "url": "https://abc.contoso.com/",
    "protocol": "http",
    "credentials": {},
    "header": {},
    "authorization": {
    "scheme": "Basic",
    "parameter": "opensesma"
    }
    },
    "proxy": {},
    "tls": {
    "validateCertificateChain": false,
    "validateCertificateName": false
    }
    }
    }

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  17. 1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  18. Provide a callback or REST API to check if changes made through management operations have been picked by Proxy

    Posting on behalf of customer:

    Per current API Management design/implementation, management operations are async and Proxy could take few sec to a minute to pickup the changes made through management APIs.
    The delay is indeterministic as there're multiple factors which could impact the time for Proxy to pickup the changes like Number of proxies involved, load on the proxy when control plane operations were made.

    As there's no deterministic way currently to confirm when Proxy has picked up the changes, we're not able to confirm if API is ready to take handle workload relying on changes.

    So, we request to…

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  19. List incremental of entities

    Hi, team
    For now, we pull our apim instances entities every day from API management service. But we can only get 1 day snap shot.
    Is it possible to get incremental values of these entities(user/operation/api/product/subscription ect.) from API management services? For example, we can get data filtered by update time?

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Service management  ·  Flag idea as inappropriate…  ·  Admin →
  20. Support expandGroups=true on the single-product GET endpoint

    The GET /products operation (in both original and ARM management REST API) supports an optional query parameter named expandGroups=true that will return groups along with each product returned.

    It would be useful to have this same query parameter available for the GET /products/{pid} endpoint when getting a specific product.

    When delegation is enabled (for product subscriptions), the delegation endpoint may need to fetch details about the product, including the groups with visibility. Currently, to get the groups for the product within the delegation endpoint, we have to make 2 service calls to the Mangement REST API. Supporting expandGroups = true…

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

API Management

Feedback and Knowledge Base