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 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” header

    Using 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 votes
    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. 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 votes
    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 →
  3. Extend the various schemas

    Having extensibility built into the user, application and other schemas would be useful for capturing the correct level of data from users

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
  4. Search API across entire site

    It would be very useful to have the search button functionality on entire site. For example, when searching an API by a word to display all related results from all available pages.

    4 votes
    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 →
  5. Conditional OAUTH prompt

    Conditional Authorization - There are situations where OAUTH prompt to be conditional based. For eg, in a money transfer scenario, if the transfer is < some amount, no authorization is required. In this case, can we add a feature in the developer portal / security to prompt OAuth based on some business rule, when a user hits try it button in developer portal

    4 votes
    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 →
  6. Allow custom identity provider portal account creation/login

    This is the same issue as as this 'completed' one: https://feedback.azure.com/forums/248703-api-management/suggestions/5947766-custom-identity-provider-for-the-developer-portal. That is only completed if you can use Azure B2C. We want to use a different identity provider (OAuth 2.0 based) to enable SSO between multiple web applications. We are currently using delegation, but that requires some integration that could go away if we could use a custom identity provider. Since there is already support for other OAuth based providers, it seems like this would be a 'easy win' for the platform.

    3 votes
    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 →
  7. Group, filter, and sort Products

    I propose to support Product grouping, filtering and sorting like APIs. One way that this can be implemented is by populating the tags of the products and make them available in the portal models (Views).
    Currently the available tags property is empty regardless of the attached to the products tags.
    The assignment of tags to products should also be supported in the relative Product edit interface of the azure portal.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    need-feedback  ·  0 comments  ·  Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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 →
  9. Try it page not handling optional route parameters

    I have this operation in my API

    "/get/{*path}": {
    "get": {
    "summary": "Get",
    "description": "Gets a single file or a collection of files and folders in a ZIP archive.",
    "operationId": "get",
    "parameters": [
    {
    "name": "path",
    "in": "path",
    "required": true,
    "schema": {
    "type": ""
    }
    },
    {
    "name": "recurse",
    "in": "query",
    "description": "Retrieve files recursively or from the {path} directory only.",
    "schema": {
    "enum": [
    "true",
    "false"
    ],
    "type": "boolean"
    }
    },
    {
    "name": "pattern",
    "in": "query",
    "description": "An expression supporting asterisks as wildcards for filtering results.",
    "schema": {
    "type": "string"
    }
    }
    ],
    "requestBody": {
    "content": {}
    },
    "responses":…

    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 →
  • Don't see your idea?

API Management

Feedback and Knowledge Base