MapQuest is committed to delivering cutting-edge solutions to our customers by leveraging the most updated technology. As a result, we’re transitioning our foundational structure to the cloud and with this transition comes updates to our current offerings.

On Monday, July 11, 2016, our direct tile access to MapQuest legacy maps will be discontinued. After Monday, July 11, 2016, we’ll require those using our direct tiles access to sign up for a plan on the Developer Network. We offer a free plan with 15,000 monthly transactions and encourage you to transition to one of our four mapping solutions after transitioning to a plan:

Please find the answers to some of the questions we anticipate around these changes below. If you have additional questions about these changes, please email us at developer-services@mapquest.com or contact us via our forum.

If I don’t sign up for a new AppKey, will my service be shut off?

If you’re currently getting direct tile access, your service will be shut off beginning Monday,  July 11, 2016. We encourage you to sign up for a plan to access an AppKey and access our various mapping solutions.

Do I have to pay to sign up for an AppKey?

We offer a number of plans including a Free option. The available plans include: Free, Basic, Plus, Business, Business Enhanced, Business Plus, and Business Plus Enhanced. Each plan gives you access to a number of great features including Leaflet Plugins, geocoding, maps, forum support and more, and have transaction limits associated with them. Please see our plans page for information about each of the plans.

What are the differences between the plans you offer?

The biggest difference between the majority of our plans is based on number of transactions. Our Enterprise-level plan includes additional benefits and flexibility. Please see our plans page for pricing and additional information. If you are interested in an Enterprise-level plan, please contact us to discuss licensing options.

How are transactions counted within your mapping solutions?

A map transaction is generally generated under the following circumstances:

  • The initial load of the map when using SDKs such as the JavaScript Maps API, Leaflet Plugins, Mobile SDKS, or legacy Flash Maps API

  • There is a change in zoom level

  • There is a change in map type, for instance, a change from the default map to satellite imagery

  • The user pans and causes more than 40% of the displayed map to change (legacy Flash Maps API only).

  • A request is made to the Static Map API Web Service.

What if I need help with the transition to a new mapping solution?

Please visit the forums on our Developer Network if you have questions about transitioning from direct tile access to Leaflet, Mobile SDK or Static Map API.

Previous Articles

MapQuest maps are getting a shiny new look. The good news? You don’t have to do anything! The even better news? Our newly styled maps will elevate the overall experience and interactions your users have with the maps on your site or within your app. Over the next month, we’re transitioning to a new, modern…

Read More

We have a lot of exciting things going on here at MapQuest. Our new mobile map SDK will allow you to deliver a fully native mapping experience across all platforms and the ability to control the look of your maps along with vector-based traffic. In addition, we’re modernizing across the board with an updated map…

Read More

Do you ever wonder what our developers are up to when they’re not working on new mapping or routing solutions? Check out what steps our development takes when improving our current API set in this recent post from Kumiko Yamazaki on DZone.    

Read More

Here at MapQuest, we’re focused on improving our products and solutions to meet our customer needs. We make a point to listen to our customers and incorporate their feedback when evaluating our offerings and prioritizing new features. Today, we’re happy to announce one of our top offerings is now available to our Business  and Business…

Read More

MapQuest plans, whether at the self-serve or Enterprise Edition level, generally operate on a quota system, in which customers purchase a set number of monthly or annual transactions. In most cases, a transaction is a request made to an underlying MapQuest service, such as a request to the Directions API or Geocoding API. To provide…

Read More

Additional MapQuest account information will soon be available at your fingertips! New features are being added over the next month to the Enterprise account management portal, helping you better manage your account and keep a pulse on your transaction usage. Previously, the number of transactions during a given time and the type of APIs and…

Read More

Nothing spoils a good user experience in a location-based application faster than an inaccurate address input. Sometimes it’s a missing a digit, other times it’s a case of searching for a street with an unusual spelling (Iliff Avenue, anyone?). One of the biggest challenges your application faces is ensuring the search query is as accurate…

Read More

Weight constraints? Height constraints? No problem. We recently added new routing options, to the avoids string collection, letting you easily avoid bridges or tunnels on your next trip. We’ve added these bridges and tunnels to our avoid string collection. The complete list now includes: Limited Access (highways) Toll Road Ferry Unpaved Approximate Seasonal Closure (Seasonal…

Read More

Sound the alarms— Location Services 5.0 is here! We’ve made big improvements to search architecture, handling and geocoding in the U.S. and Canada in order to provide more accurate geocoding results for your applications. So, what does this mean for you? Simply stated, we’re helping you create a better experience for your users. We’re hyper-focused…

Read More

Follow @MapQuestTech on Twitter

MapQuest DevBlog RSS

Want to stay updated on all the latest advances? Subscribe to our blog feed and be among the first to receive the news!