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.
-
New API Management developer portal
We are working on a new, open-source developer portal offering in Azure API Management, based on our own fork of the Paperbits framework (paperbits.io). It has a modern default look and feel, and is optimized for:
- Customization, styling, and authoring through a built-in visual editor
- Programmatic access through APIs for automating development, management, and deployment
- Extension of the provided core functionality
359 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)
303 votes -
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.
269 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:
93 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…
77 votes -
Single Swagger file for all APIs
Support producing/exporting a single Swagger file for all APIs within API management.
62 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".In the…
51 votesPlease upload an OpenAPI file illustrating the issue.
-
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.
48 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…
37 votesGrouping is now available for APIs and operations. We plan to add same functionality to products too.
-
Client certificate authentication in developer console
If the front-end takes mutual certs, the console cannot provide a way for developers to test API.
35 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 -
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
23 votes -
Set FROM address for e-mail notifications
Right now e-mail notifications are sent with a from header "Windows Azure API Management". Allow users to change the e-mail address placed in the FROM header to match their company addressing.
23 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.
22 votes -
Filtering APIs and operations based on tags
1. Is it possible to see on the APIs page, while trying to filter based on tags, just the tags correspondent to the APIs and not also the tags defined for operations? (If an user of the API portal will want to filter the APIs it will be difficult to choose a proper tag value because there are, for example, more than 30 tags into the drop down and the actual tags for the APIs are for example just 4-5 … )
2. Is it possible not to see the tags defined for APIs into the operation page while trying…
18 votesThanks for the feedback. We will improve the user experience when there is a large number of tags defined.
-
Display description included in JSON schema
It's great that we are able to provide JSON schema for request definitions. As we are using the "description" property in our request schema to give some useful hints regarding each property, it would be nice to have this shown in the developer portal (like it is done in the "Model" view of swagger UI). Currently the descriptions are a bit hidden in the schema definition and not so obvious for the developers.
19 votes -
Developer-facing UX for Basic Auth credentials
Today, APIM provides a nice developer-facing UX for acquiring OAuth 2.0 access tokens – specifically, a dropdown is rendered on the Console page with whatever supported grant types have been selected for the Authorization Server associated with the API.
But for APIs that use a Basic Authentication security model for user-level authorization, there is no similar developer-facing UX. So this means that developers using the portal have to manually click “Add header”, select “Authorization”, and then specify the base-64 encoded value for their username:password. That works fine, but it’s a little cumbersome.
It would be nice if APIM could provide…
15 votes -
API Management Swagger Definition does not give model details.
I have imported swagger definiton file into APIM Publisher portal. It shows different actions but there is no info about navigation property from an entity which is specified in the Entity Framework model. I would want to publish that information on developer portal as well. See the attached picture.
13 votesHi, the picture seems to have been lost, can you please resend?
-
Add "Remember Me" feature to OAuth Resource Owner Password grant type in the Developer Portal
Add a "remember me" checkbox to the OAuth Resource Owner Password grant type so that it reuses the access token for other "Try It" attempts for any other API operations instead of requiring the username/password for every operation.
13 votes -
Provide named values to the templates
Would it be very useful if "named values" (global parameters you can use inside policies) could be used inside dotliquid templates ie.
{{ myCustomNamedValue }}. This is important to link to external resources (in development / production envs), or to display values to the users (ie. quota limits) you use in policies as well.
13 votes
- Don't see your idea?