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.
-
POST "Comments- Add" Api issue on this api
When we are using this Api, its returning status code as "Ok" and i am able to see the response with Comments Added, but i am not able to see those comments in workitem at AZDO. Can you suggest, why this happening? and what is the cause for it?
1 vote -
Meticore Reviews 2020: Meticore Weight Loss Diet Pills
Your order today is protected by my 100% Money Back Guarantee. If you are not 100% satisfied, if you do not FEEL the energy as your unsightly belly fat melts away... if you do not SEE the results in the mirror every day and finally ENJOY your life with FREEDOM to it's full, **** and confident potential https://meticoretrigger.blogspot.com/
1 vote -
Add indicator for which item is used
When working with the new DevPortal checking which images are used in a certain widget comes in handy, when having many images uploaded
1 vote -
Url Helper Policy Expressions for Route Building
As a developer I want to include hypermedia links to other operations in the same and other API sets so that I have easy navigation for clients between APIs.
Today, these link url paths must be hard coded based on what is know. To provide flexibility while developing APIs and to ensure routes are actually valid, provide a url helper method to generate these routes.
Example:
context.RouteFor("API-ID", "Version", "Operation-ID", new {param1=1,param2="hello"})
Today:
<set-body>{
return JObject.FromObject(new {_links = new[] {
new { href = $"/api/operation?query={context.Request.MatchedParameters.GetValueOrDefault("query", string.Empty)&api-version=2018-10-31", rel = "other-api", type = "GET" }
}}
}</set-body>With a helper:
<set-body>{ …
1 vote -
Support for token bucket - enable burst quota
The current quota/call rate limit is +1 per call. In practice this means we create SKUs based on the maximum expected spike rather than average usage. By supporting a token bucket model (https://en.wikipedia.org/wiki/Token_bucket) we could define a SKU more aligned with our actual usage.
For example: on average we have 50 calls per second, but need to be able to spike to 250 calls per second.
Today we'd create a 250 calls per second throttle policy for this key/product which is not optimal.
1 vote -
Support for importing OpenApi spec file greater than 4MB in size
API import using File upload method does not work for files greater than 4MB in size. I don't find this limitation in any of the Azure documents but I see only in the Portal as shown in the attachment.
We have OpenApi spec files of size greater than 4MB and not able to use the file-based import method.
This request is to support API import of files greater than size 4MB.
1 vote -
Can you add System.Security.Cryptography.X509Certificates into whitelist. So it can be used to verify certificates.
System.Security.Cryptography.X509Certificates is required to verify if a certificate is revoked or not and also validate the certificate chain.
1 voteHi Mohamed! You can validate a client certificate using context.Request.Certificate.Verify() which will check both its validity a revocation list. Does this address your scenario?
-
Allow control over publisher notifications
There currently is no control over publisher notifications. Developer notification functionality could be replicated for publisher notifications. A small example is in Organization Name, this can be changed for developer notifications but not for publisher notifications.
1 voteHi David, Notifications page allow publishers to configure email notifications about various system events. Is that what you are looking for?
-
add ability to mark a header or parameter value as private
We have additional credentials that are configured to be passed as additional headers. It would be nice to be able to mark these as "private" in the configuration so in the "try it" page the values that are typed in are handled like the subscription key and they appear as dots when typed. Right now when we're doing a screen share demonstration, people watching the demonstration have full view of the username and password being entered. Sure, we can go through special means to have dummy accounts or dummy systems, or change the credentials as soon as the demo is…
1 vote -
Want API subscriber email request to show what environment they are wanting to subscribe to.
Prior to April 1, 2020 the potential API subscriber email included the environment of the API service that they are wanting to subscribe to. This is no longer being shown in the emails and we would like this feature back please. Please view attached emails to see what has changed.
1 vote -
API returns with upper characters even though the resource group name is lower characters
I am trying to hit API which is in hostgroup using powershell and in the response you are able to see the resource group name in upper case but I have defined it in lower case. How can I get the response with the defined one.
1 vote -
Azure AD B2C Sign in and Sign up button in Developer portal
Azure AD B2C Sign in and sign up buttons should be added in the portal so that we can use it anywhere such as in custom pages or menubar of the developer portal.
Currently, Azure AD B2C sign in button is only available for in-built Sign in page.1 vote -
Policy tag directory
Have a comprehensive directory that has all of the tags that can be used in the policy XML.
An example is have documentation of the <when> tag regarding which tags can be nested within and which attributes it accepts.
I seem to be unable to find any resource that has detailed documentation on these multi-use tags.
Thank you
1 vote -
Base an API revision off a git branch
This may be possible I'm not sure but it would be useful if you could add a revision to an API or the entire API management and have it based of a branch in the git repository. This would allow a side by side API based on your staged changes and allow you to test in a blue/green scenario. Once the API is tested if you could make it public.
1 vote -
By adding documentation for REST Interface , Multi Client and self signed Certificate authentication
Documentation for REST Interface is very confusing as;
1) ARM specific operations and urls are mixed together with APIM service instance specific endpoints and operations.
2) PUT operations are titled as "Create or Update" operation while PATCH operation are marked as "Update" operation. This is confusing and costed us an outage; "Update" operation should be named as "Partial update" or "PATCH" operation in title. example:
https://docs.microsoft.com/en-us/rest/api/apimanagement/2019-12-01/apimanagementservice/createorupdateUsually,
POST operation is create operation
PUT is update
PATCH is partial update3) also the documentation should explain all the possible values of property attribute like
"virtualNetworkType": "None". //in documentation
"virtualNetworkType": "External" //not…1 vote -
Fix the terminology
Our team just spent a whole day looking for ways to update Named Values programatically. In the end we found the way to do it with management APIs. The reason it was so hard to find, because it's not called Named Values in the management API, it is called
properties. Now this is confusing, because the GUI for APIM also has a section namedpropertiesthat has nothing to do with named values.
It would help a lot if your GUI and management API would use the same terminology.1 voteFair point. Thank you for the feedback! We added this suggestion to the backlog and will update the item when we prioritize it for implementation.
-
Ability to reset developer portal style.
Add the ability to reset developer portal style to default style.
1 vote -
Allow to import OpenAPI document with remote references
As per currently known API importing issues, $ref pointers from the OpenAPI specification can't reference external files. However, it could be a crucial feature to standardize APIs across an organization. As is we can certainly make it a local reference but it enforces duplication and becomes difficult to manage length OpenAPI documents. Hence please allow to import OpenAPI documents with remote references.
Known import issue reference: https://docs.microsoft.com/en-us/azure/api-management/api-management-api-import-restrictions
1 vote -
Fix: Autogenerated "name" in new operation doesn't strip invalid characters
add this as displayname:
/path/routePath/{parameter}
This gets auto-generated as name
path-routepath-{parameter}
But that auto-generated name is invalid because of the brackets. The auto-generation process already changes slashes to dashes, so why not also make it strip out invalid characters?
1 vote -
Use valid xml to configure policies.
In your examples one can find lines like this one:
<set-variable name="isMobile" value="@(context.Request.Headers["User-Agent"].Contains("iPad") || context.Request.Headers["User-Agent"].Contains("iPhone"))" />If you try to validate this xml, you will find out that those double quotes inside of the value attribute are not allowed.
1 vote
- Don't see your idea?