Bing Maps API key suddenly refused RRS feed

  • Question

  • Hi,

    I have a public application that uses a Bing Maps key generated through the Azure portal (Bing Maps API for Enterprise, Public Website Transactions Level 1). This key is fairly new (~2 weeks).

    As from today, all Bing Maps API requests return 403, "authenticationResultCode":"DeniedCredentials".

    What's the reason for that? What can I do about it?


    Friday, August 4, 2017 3:12 PM


All replies

  • Contact the Bing Maps Enterprise support team. Contact details can be found here:

    There are a few reasons why this would happen. The most common is that your application has exceed the purchased volume of transactions. 

    [Blog] [twitter] [LinkedIn]

    Friday, August 4, 2017 3:59 PM
  • Apparently there is no way (yet?) to follow the usage of a key generated through the Azure portal.

    And leaflet plugins for Bing are very naive when it comes to transactions: every layer asks for the same metadata, which counts for a transaction. In our application we can easily have up to 20 layers per page, so the volume goes up very quickly. I went about creating my own plugin (not yet opensource).

    Thanks for your answer.

    Monday, August 7, 2017 8:40 AM