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.
-
GraphQL introspective support within API Management
Like swagger documents which describe REST endpoints, we would like to surface graphql queries and mutable schemas and types through the Developer portal.
1,299 votes -
API / Operation visibility
Make possible to manage the visibility not only at product level but also at API level (and even maybe at operation level)
558 votes -
Controlling Signup button functionality
Currently there is no support to disable Signup functionality. If we disable Identities, it disables the Login also.
There must be a way to achieve this. Refer below link for more details:
103 votes -
Ability to Group Subscription Keys
Currently the subscription keys are issued at the 'Product' level. These products basically map to resource features. It is great that subscription is managed at this granularity but it would be better if the subscriptions can also be managed at higher levels. I may want to use the same subscription key to Axcess multiple products (or bundles) or even go to a higher level of managing APIs at multiple bundles level (or container) with a single key. This way the developers can use the same subscription key across products, bundles or container levels as configured by the publisher of the…
99 votes -
Single Swagger file for all APIs
Support producing/exporting a single Swagger file for all APIs within API management.
89 votes -
Add Developer Portal to Consumption Tier
Please add the developer portal to the consumption tier.
It's currently very confusing in the management portal as to what is supported and what isn't when using the consumption tier. For instance, it is possible to publish products, or define definition's for responses, yet this seems to only be for publishing in the developer portal.
This article: https://docs.microsoft.com/en-us/azure/azure-functions/functions-openapi-definition comes close to explaining how to set up at least an OpenAPI definition - but it dosen't appear possible to link multiple existing Azure functions to an existing API Management gateway.
Is the developer portal feature (in all other tiers) going to…
89 votes -
Manual order/grouping of operations
It'd be great to be able to manually order and/or group operations within an API for easier usage.
59 votesThanks for the feedback. Can you please provide a little more details on how you want this to work? Do you want this feature on developer portal or admin portal or both? Thanks!
-
Support better grouping & sorting of products & APIs
Right now - everything is forced into alphabetical sorting. There are no grouping options. We plan to use this for our entire enterprise, and we expect to end up with hundreds of APIs and dozens of products. A simple "sort order" field will accomplish the sorting issues, may be cumbersome to maintain but we could manage. Not sure how grouping would work, but here is our example:
Products:
Business Unit A - Developer
Business Unit A - Test
Business Unit A - Production
Business Unit A - Production UnlimitedI may like to have a "bucket" named just "Business Unit…
56 votesGrouping is now available for APIs and operations. We plan to add same functionality to products too.
-
Ability to Secure New Developer Portal Pages
In the new developer portal there is no way to secure pages from being viewed. If i want to add supplementary api documentation pages in the portal I cannot specify to only allow that page to show when the user is logged in. The only real security in the portal is that apis and products won't show based on whether the user is logged in.
The only capability present is to hide them in the navigation menu. So if I add a page at /apis/project/order. I can place it in the menu and say whether it will show up there,…
52 votes -
Support in "produces" section the Accept-Header from OpenAPI specification
The produces/consumes is MIME type.
1. The “consumes” specify the format that the API can accept. So “consumes” only affects operations with a request body, such as POST, PUT and PATCH.
And is sent via “Content-Type” header
2. The “produces” specify the format that the API can return.
And I sent via “Accept” headerUsing the “Accept” header the user can select needed API response MIME type (e.g. "text/plain", "application/octet-stream", "/").
When sending a request with SwaggerUI, We can selecte "application/octet-stream" Response Content Type.
The request was sent by Swagger UI with the “Accept” header value filled "application/octet-stream".…
51 votesPlease upload an OpenAPI file illustrating the issue.
-
Client certificate authentication in developer console
If the front-end takes mutual certs, the console cannot provide a way for developers to test API.
47 votes -
How do I Publish developer portal changes from one apim instance to other?
As per the new developer portal feature, you can make changes to APIM layout and publish to APIM repository, the same repository you can clone to your local machine using git clone but we don't have a feature where in we want to publish our developer portal changes to one API management instance to other API management instance.
e.g.:
I have 2 instance : dev-01-apim, tst-01-apim
I am making changes to dev-01 instance of developer portal ..after all my changes now I want to move those changes to my test instance of pain.how do I do that ?.
44 votes -
Support for multi-tenant user login delegation
In a multi-tenant scenario, there is no option to delegate user login to multiple urls, the delegation section allows only one url.
It would be great if it would allow one delegation endpoint per custom developer portal domain.
43 votesHi, can you please provide more information about your scenario? Thanks.
-
Developer portal - View the published portal without private browsing mode
When accessing the new developer portal in Azure API Management in the same browser session in which being connected to Azure, the administrative version of the portal is opening.
However, developers of my team use to develop API, but also to consume it. So it would be preferable to view the portal directly in published mode (like the old developer portal) rather than opening a new private browsing window, and logging into Azure (that is a long process in my company, because of MFA).
It would be awesome to have the ability to click on another button to access directly…
35 votes -
API change log with notifications
Automatically provide a change log per API & operation when changes are made to the API (including full replacement via Swagger). Also have the ability to send developers with subscriptions to products linked to an API an e-mail with change notifications on time-scale they choose (daily, weekly) or when pushed by admin.
33 votes -
Register app with Azure AD through developer portal
Given that there are already integrations with Azure AD, it would be developer friendly if you could register and manage your apps with Azure AD through the developer console.
That way you would need just one portal to deal with things like client ids, secrets etc
32 votes -
Allow developers to upload API Management code samples
We have started using new developer portal and realized there is no way to add new language samples and edit existing templates. Could you please add a feature to add new language templates and update existing items.
29 votes -
Send an email to a user once their subscription has been activated
When a developer subscribes to a product that requires activation, they're not currently notified when their subscription is approved.
28 votes -
[Developer portal] bring back Issues feature
Would be nice to reintroduce the 'Issues' feature from the legacy portal into the new developer portal.
26 votes -
Support application/x-www-form-urlencoded parameters representation
x-www-form-urlencoded parameters are currently not displayed at the developer portal. therefore the developer wont know what is expected of him to send.
Current workaround is adding it to "sample" in the apim.
But this is not scaling as it is a manual fix that needs to happen each time a developer uploads an openapi spec containing body parameters of this type.23 votes
- Don't see your idea?