The gap between "Developer" and "Standard" is huge.
Developer: 32K calls/day
Standard: 6600K calls/day (206 times what developer gives!)

This isn't flexible at all. Of course 90% of everyone will fall between these two options and therefore will have to buy the expensive one, meaning in practice that 90% of everyone won't use the service at all and just roll their own.

What about a Basic Tier?
1000K calls/day
210$/month

managing webhooks under api management will get us more control around who is allowed to do what: http://blogs.msdn.com/b/webdev/archive/2015/09/04/introducing-microsoft-asp-net-webhooks-preview.aspx

It is a common practice for API service developers to link the resource counts or product plans to pricing. The preference is for either integration ability to 3rd party services (ex. Braintree) or direct implementation so API developers can collect payment for services.

We need a developer free tier to dabble around with API Management.

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.

Today, when creating a new API there is the Help area in the solution that provides a light documentation of the API. Please add a simple way to export this to API Management.

Having the ability to regulate and monitor HTTP services with API Management is great. Wouldn't it also make sense to offer the same for web sockets (or SignalR hubs, etc.) so we can let devs hookup into stream of events (live-data) instead of polling with REST calls?

A cloning option for the full api could be helpful for this.

While the features of API management are nice the current pricing model would excludes those who are in BizSpark trying to stay within the monthly $150 monetary cap. Based on the current pricing of ~$49/month for dev and ~$349/month for standard, dev would consume about a 1/3rd of the monetary cap and standard would completely nuke it from orbit exceeding the cap by 2.3x all by itself.

I’d be nice to see pricing come down to some reasonable limits preferably with a free dev and standard tier matching the current pricing of the dev tier.

When adding descriptions to operations or request & responses all formatting is ignored, even line breaks. Makes it difficult to provide any sort of useful documentation for people to read. Should support markdown or html at least.

Right now the only people who can edit/create APIs have to be full administrators on the entire Azure Subscription. I need to be able to delegate administrator privileges on the api-portal without giving them the keys to the whole castle.

Add support to import raml specs

I'm attempting to front a ASP.NET WebAPI with the Azure API Management service. My WebAPI supports the notion of optional URL fragments.

See my Q on the User forum:
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/e2faaf9c-b9d1-4ef9-9c35-b466f3b95a82/how-can-i-specify-optional-url-template-parameters?forum=azureapimgmt

The workaround suggested works, but will end up bloating my API operations significantly.

Headers are not first class citizens when modeling API operations. There is no clear place to enter or describe them. The resulting header documentation on the Dev portal is poor.
How about treating headers like you do with query string parameters, so users can add as many as required and they are pre-populated with default values when using the API test utility?

Support import of API definitions and metadata from OData $metadata.

I would like to have a way to select the operations that I want to share from a particular Api for a product. Currently if I create a product and select an API all the operations are exposed. So If I need another product with some of the operations from this API, I need to create them all again, Which is a huge rework.

Please some comment if there is a way to achieve this.

I'd like to be able to specify an "account id" on each developer (some developers may share the same account id/channel id) which is then passed down to the backend system for accounting and control.

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:

https://social.msdn.microsoft.com/Forums/azure/en-US/3b8c8c60-0e26-4d7f-9a6f-2f2bc6b84bf2/how-to-disable-signup-button-functionality-on-developer-portal?forum=azureapimgmt

Managing APIs should not require co-admin rights. Provide a reasonable set of default roles (admin, reader, writer) and enable admins to define custom roles giving users granular rights to entities (apis, products) and actions over them.