MapQuest Developer Blog

  • MapQuest Free & Open License Updates and Changes

    As a user of the legacy MapQuest Free & Open license, we want to let you know about upcoming changes in licensing that may affect you and your application. To ensure that we can continue to offer the best service and product lineup possible, we are transitioning to a new licensing structure that will ultimately require our users to sign up for one of the plans available on the Developer Network by Tuesday, September 15, 2015. In addition, to bring our hosted versions of Nominatim and Xapi into line with the rest of our Open Data API and SDK product line, we are going to start requiring an AppKey to be submitted with Nominatim and Xapi requests. Please find the answers to some of the questions we anticipated around these changes below. If you have additional questions about these changes, please email us Why are you moving away from offering Open services? We are not moving away from offering our users access to Open Data. We are making changes to our Open APIs and SDKs to ensure we can continue to offer our users the best possible product. We’re removing unlimited access and requiring people to sign up for an AppKey based on their specific needs. We still offer free access through a plan that limits users to 15,000 transactions per month. In addition to the Open access, our users will also have access to our licensed Data. Are you going to remove the Open Data APIs & SDKs from your product lineup? No. We will continue to offer the option of accessing our underlying services that utilize our Open Data source. However, to bring our Open Data APIs and SDKs in line with the rest of our product offering, we are no longer offering the option of unlimited use of the Open Data APIs and SDKs. How can I tell if I have a legacy Free & Open key? Legacy Free & Open keys begin with the letter ‘F’ or the letter ‘D’ and were available prior to May 1, 2015. I’m using a legacy Free & Open key. What will happen to my key? Legacy Free & Open keys will be converted to our current free plan, which is detailed on the Plans page on the Developer Network. The free plan allows access to both Licensed Data and Open Data APIs and SDKs and allows up to 15,000 transactions/month. Existing legacy Free & Open keys will be migrated to the free plan on Tuesday, September 15, 2015. Why are you requiring an AppKey for Nominatim and Xapi? Our other Open Data APIs and SDKs already require an AppKey and we want to bring Nominatim and Xapi into line with the rest of our Open Data (and Licensed Data) API and SDK product offerings. Requiring an AppKey allows us to do a few things:
    1. It gives us greater insight into how our clients and overall developer community are using our products.
    2. We can ensure that our product roadmaps are aligned with the features that are highly used and most valuable to our clients and the developer community.
    3. We can contact our clients and overall developer community to better communicate news regarding Nominatim and Xapi, such as planned maintenance or system upgrades.
    We’re setting the stage to offer an even more compelling product line in the future– one that is a mixture of new products, new features, and enhanced existing features. If I don’t sign up for a new AppKey, will my service be shut off? If you are currently a legacy user with a Free & Open AppKey, we will automatically move you to our free plan. If you anticipate needing more than 15,000 transactions per month, we recommend upgrading now. If you don’t upgrade and get close to your transaction limit, we will email you with information on upgrading so there isn’t a disruption in service. If I don’t sign up for an AppKey, will my access to Nominatim and Xapi be removed? Yes. If you are accessing Nominatim and Xapi without an AppKey and do not sign up for a key by the September 15, 2015 deadline, requests to Nominatim and Xapi will fail and your application will be impacted. While Nominatim and Xapi won’t be ‘shut off,’ you will be unable to access the service without providing an AppKey with your requests. What if I need help with implementing my AppKey? Please visit the forums on our Developer Network if you have questions about providing an AppKey with your Nominatim and Xapi requests. Will the changes announced today affect the availability of your Open Map Tiles? At this time, we don’t have any changes to announce regarding our Open Map Tiles.
  • Planned Outage for Nominatim Search Service

    As many of you know, MapQuest hosts a version of the Nominatim Search Service as a part of our Open Data API and SDK product line, so we wanted to share an important update about this service that will have an impact on users of this service.

    The Nominatim Search Service will be unavailable on Tuesday, August 18, 2015 due to system maintenance. While it is never our intention to cause service disruptions, the outage is necessary. We apologize for the inconvenience that this will cause to our users of Nominatim. Please email us at with any further questions.  
  • Introducing the new MapQuest Developer Network!

    We’ve been working on a number of infrastructure upgrades over the past few months and recently released one of the most visible updates: the new MapQuest Developer Network! The new Developer Network -- along with a quite a few other important upgrades -- sets the foundation for a much-improved developer experience that will be rolled out in phases throughout the rest of the year. developer-network-072015 First, the information architecture of the site has been changed and additional content has been added. We want to ensure that our documentation is easy to find so that it is easy to get started while keeping the number of clicks to a minimum. Our documentation is available via the Documentation link on the homepage. Second, we more prominently highlight the types of solutions in which our APIs and SDKs are commonly integrated. We like to think of our APIs and SDKs as building blocks -- or better yet, a toolbox -- since the APIs and SDKs can be mixed and matched to create truly custom, full-fledged applications. The best features of each API and SDK are detailed in the Products section of the site. Third, we’ve launched our Plans page, which offers the ability for Developers, Startups, and Small Businesses to sign up for a monthly paid subscription that goes beyond the 15,000 transactions/month offered in our Free plan. The paid subscription plans offer access to all APIs and SDKs included in our geospatial toolbox without the need to contact an Account Manager during business hours. The Plans page is available 24 hours/day, 7 days/week, and it is easy to sign up and get started. There are a number of items on the Developer Network roadmap that will be introduced later this year, such as:
    • standardized API Web Service documentation, using a common format that makes it even easier to form API requests and understand API responses
    • additional demos that showcase our APIs and SDKs working together to create a full-scale solution, complete with downloadable code
    • enhanced Developer’s Guides for our Map SDKs with re-worked ‘try-it-now’ samples
    • additional Plans that include access to new APIs, SDKs, and other services provided by MapQuest
    Stay tuned for additional information about new products, upcoming Developer Network enhancements, as well as other improvements to the overall MapQuest developer experience. As always, feel free to drop us an email or tweet us @MapQuestTech if you have questions.
  • Looking for a Free & Open AppKey? Read This.

    Within the next few weeks, MapQuest will unveil a completely revamped Developer experience. While we prepare for these exciting upgrades, we will be making critical infrastructure updates and will be pausing the creation of new Free & Open AppKeys on the Developer Network as of today, May 1, 2015. If you currently have a Free & Open AppKey and are currently using our Free & Open APIs and SDKs, your AppKey will continue to function as usual. If you would like to evaluate MapQuest Enterprise Edition services, please contact us through the Developer Network or contact an Account Manager at 1-888-895-8742 to request an evaluation Enterprise Edition AppKey. Finally, if you have questions, please feel free to get in touch on the MapQuest Developer Forums or send us an e-mail. Stay tuned for announcements on this blog regarding updates and other opportunities to learn more about improvements to our Developer experience!
  • 3 Reasons MapQuest’s Enterprise Product Suite Should Power Your Business

    Let’s face it. In the mapping space, you have options. But not all options are created equal, especially when it comes to your business needs. Beyond reliability, accuracy and legacy, here are the three reasons that MapQuest Enterprise is truly the only option you need:

    1. No daily limit on service: Unlike the Community Edition license, an Enterprise Edition license doesn’t have a daily limit on usage.  Enterprise Edition clients don’t need to worry about service interruptions due to our service shutting off after the 5,000th transaction of the day.

    1. Access to experts: Whether it’s a technical support issue or implementation advice, our team of experts can help our clients get the most out of an Enterprise Edition license.  If problems are encountered, 24/7 Emergency Support is available.

    1. Peace of mind: No need to question whether our services can meet increased traffic and demand from your application; an Enterprise Edition license gives your application access to our APIs and SDKs hosted on Enterprise-grade infrastructure that can scale to meet demand.  An Enterprise Edition license also includes a service-level agreement (SLA) and guaranteed uptime.

    From geocodes to maps to routing matrices to big data and search, MapQuest has a custom solution to drive your business forward. And while we currently serve thousands of enterprise customers globally, contact one of our account managers today to learn more or tweet us @MapQuestTech.  
  • Are you a Community Edition (Licensed Data) user?

    Attention, users of Community Edition on Licensed Data! We are in the process of simplifying our licensing structure and have a few upcoming changes that we want you to know about. Currently, MapQuest offers three types of licenses for use of our APIs, SDKs, and associated Developer Tools: Community Edition (Open Data), Community Edition (Licensed Data), and Enterprise Edition (Licensed Data). Later this year, we will be simplifying the structure by removing the Community Edition (Licensed Data) tier. As of December 31, 2014, we will be retiring the Community Edition (Licensed Data) license in favor of two tiers: Free & Open (Open Data) and Enterprise Edition (Licensed Data).
    Current Structure as of December 31, 2014
    Need a refresher on the difference between our Licensed Data and Open Data sources?
    Community Edition (Open Data) Community Edition (Licensed Data) Enterprise Edition (Licensed Data) Free & Open (Open Data) Enterprise Edition (Licensed Data)
    What does this mean to you? If you are currently using a Community Edition AppKey (a key that begins with the letter “F”) with our Licensed Data APIs & SDKs, you have the following options:
    • Become a MapQuest Enterprise Edition client by reaching out to an Account Manager at 1-888-895-8742 or using the ‘Contact Us’ form on the Developer Network. Our Enterprise Edition platform offers the scalability and performance necessary to support enterprise-level applications, a dedicated Account Manager, technical support and implementation advice, and the types of SLAs necessary to support businesses of all sizes. Enterprise Edition (Licensed Data) APIs and SDKs are accessed from the domain.
    • Move to a Free & Open (Open Data) license by taking a look at our Open Data APIs and SDKs, which are very similar to the current Licensed Data APIs and SDKs, but offer crowdsourced data, most of which is provided by the OpenStreetMap community. Unlike our Licensed Data APIs and SDKs, our Open Data APIs and SDKs give you access to the underlying map data, which can be edited and updated by you. Free & Open (Open Data) APIs and SDKs are accessed from the subdomain.
    After December 31, 2014, current Community Edition AppKeys will stop working with our Licensed Data APIs and SDKs, but will continue to work with our Open Data APIs and SDKs. It is important that you make changes by December 31, 2014, or you may experience an interruption in service. Current Enterprise Edition (Licensed Data) clients are not affected by this change, but, if you are an Enterprise Edition client and have questions, please feel free to reach out to your Account Manager. This is just the beginning of a few exciting changes you will be seeing over the next few months -- so stay tuned, and as always, feel free to check in on our Developer Network forums or tweet us @MapQuestTech if you have questions!
  • Nominatim/OSM Data Updates Temporarily Suspended

    Attention, users of the MapQuest-hosted Nominatim Search Service! During the next few weeks, we will be making upgrades to the back-end systems that power our instance of Nominatim and this involves a complete data refresh. During this time, OSM data updates will be temporarily suspended. It is possible that users may temporarily experience inconsistent results until all of our back-end servers have received the necessary upgrades. It is also possible that users may not see recent edits to OSM data immediately reflected in search results. Please feel free to tweet us @MapQuestTech or e-mail us at to ask questions. We apologize for any inconvenience caused by the temporary suspension of data updates! UPDATE: As of September 15, 2014, upgrades to our back-end infrastructure have been completed and OSM data updates have resumed.
  • JavaScript Maps API v7.1.0 Released (Licensed & Open)

    Today we are excited to announce quite a few JavaScript Maps API updates! The JavaScript Maps API v7.1.0 and Open JavaScript Maps API v7.1.0 have been officially released to production and include a great mix of new functionality as well as enhancements to existing functionality. We’ve also simplified and updated our list of currently supported browsers. First, let’s talk about new functionality. We’ve introduced new, easy-to-use routing modules to the toolkit. The new-route and new-route-collection modules include the ability to more easily customize the start and end POI icons on the route by using POIs as input to routes. We’ve also added the ability to manually create a route and add it to the map by providing the coordinates that make up the shape of the route; the bonus is that the manually created route then takes on the characteristics of a route generated by the toolkit, so features like draggable routing can be used. Be sure to check out the routing section of the JavaScript Maps API v7.1.0 Developer’s Guide to see the new routing modules in action. Better yet -- use the Try-It-Now samples to get a quick taste of working with this new functionality. Second, this release includes quite a few enhancements especially related to compatibility with browsers on mobile touch devices. From touch events to pinch zooming, we’ve spent a considerable amount of time refining the modules that support the toolkit on mobile touch devices. Updates were not limited to support for mobile touch devices; for a full recap of updates that have been made and issues that have been addressed, please refer to our release notes. Finally, the Developer’s Guide and API Reference Guide received updates as well. The Developer’s Guide includes new samples that highlight the functionality offered by the new-route and new-route-collection modules and the API Reference Guide has also been updated accordingly. We’ve also revised the look and feel of the API Reference Guide to provide a better experience for our developers by making information easier to find. We’d also like to note that all previous versions of the JavaScript Maps API (7.0.0 and 7.0.1) are officially deprecated. We encourage everyone to upgrade to version 7.1.0, which is now the current supported version of the JavaScript Maps API. Feel free to let us know what you think by posting on our Developer Network JavaScript Maps API Forum or reaching out to us on Twitter @MapQuestTech! Note: The new-route and new-route-collection modules are not the default routing modules in 7.1.0. The routing modules from the JavaScript Maps API 7.0.1 are still default in order to preserve backward compatibility, since code changes are needed to use the new-route and new-route-collection modules. For more information, see the JavaScript Maps API Developer’s Guide.
  • Announcing MapQuest Plugins for Leaflet on Licensed and Open Data

    Did you know that MapQuest offers the ability to use our maps, geocoding, and routing with the open-source Leaflet mapping library? The interest and feedback provided during our public beta was truly overwhelming and today we are excited to announce the first production release of the MapQuest Plugins for Leaflet, utilizing both our Licensed and Open data sources. The MapQuest Plugins for Leaflet enable developers to easily integrate our most popular core services -- maps, routing, and geocoding -- to applications built with the open-source Leaflet JavaScript mapping library. What's not to like about that? Today we're offering production releases of the following plugins:
    • Maps - While many developers were already using MapQuest-OSM and Open Aerial Tiles with libraries like Leaflet and OpenLayers, we've never been able to offer access to our map tiles that are created from licensed data sources. The MapQuest Maps plugin for Leaflet allows you to do just that; it allows you to use our licensed map, satellite, and hybrid tiles with Leaflet. It's also easy to use the Leaflet layers control to switch between each map type. Don't worry, we're also offering an Open version of our Maps Plugin, which makes it even easier to add and use our Open Tiles with Leaflet.
    • Geocoding - The MapQuest Geocoding plugin for Leaflet takes care of the heavy lifting for you. You can easily integrate Licensed or Open MapQuest geocoding functionality into Leaflet, as it takes care of making requests, parsing responses, and adding results to your map.
    • Routing - With the MapQuest Routing plugin for Leaflet, you can easily integrate Licensed or Open MapQuest routing into Leaflet, including our popular draggable routes functionality. Aside from draggable routes, this plugin also offers many of the features that our developers expect, such as our extensive route options, optimized routes, and multipoint routes.
    The MapQuest Plugins for Leaflet allow developers to have the best of both worlds: use of a well-supported and extremely popular JavaScript mapping library and the easy integration of the core services that MapQuest is known for. In addition to the production release, the MapQuest Plugins for Leaflet Developer's Guide has been updated to include the Try-It-Now functionality this is part of our other Developer's Guides. With Try-It-Now, developers can easily access and experiment with the code that powers each of the samples. We've also added information about accessing the plugins that utilize Open data. A key is required to use the plugins, but usage of the plugins is free, just like our other MapQuest Open services. Got questions? We've got answers. Feel free to tweet us @MapQuestTech or post a topic on our Developer Network Forums. We love to hear from our developers, so don't hesitate, get started today!
  • Are You Using an Older (Licensed) MapQuest API or Developer Tool?

    We are in the process of retiring some of our legacy back-end systems and want to let you know what that means to you as a user of MapQuest APIs and developer tools that utilize licensed data. Effective January 31, 2014, the servers that power legacy products -- mostly those that operate in the Equirectangular map projection -- will be retired.   This means that older APIs and SDKs, such as the deprecated server-side SDKs and 5.x JavaScript and Flash APIs, will no longer work.  To avoid an interruption in service, please ensure that your applications are using our current Web Services and Map APIs. Enterprise Edition clients have already been notified about the Enterprise Migration, so if you are a MapQuest Enterprise client and have questions or need assistance with migrating to our latest and greatest product offerings, please reach out to your Account Manager or the Enterprise Technical Support Team. Community Edition developers have been notified about the migration as well, though it is difficult to confirm that we have reached every Community Edition developer.  While a Community Edition license does not include access to an Account Manager or the Enterprise Technical Support Team, help from other MapQuest developers (and the occasional MapQuest employee) is always available in the MapQuest Developer Network Forums. If you are using any of the MapQuest Web Services that operate on licensed data, you should be making calls to the following versions:
    Directions API Web Service or later
    Geocode API Web Service or later
    Search API Web Service or later
    Static Map API Web Service or later
    Traffic API Web Service or later
    If you are using any of the (Licensed) MapQuest Map APIs (Map Toolkits), you should be using the following versions:
    JavaScript Maps API 7.0.1 (7.0.s) or later
    Flash Maps API 7.1.2c or later
    Mobile Flash Maps API 7.1.2c or later
    iOS Maps API 1.1 or later
    Android Maps API 1.0.5 or later
    If you are using the Data Manager Tool that is available through the “Manage AppKeys” section on the Developer Network, you should migrate your data to the spatially-aware Data Manager API Web Service, which offers the ability to store spatial data as a native geometry data type. Finally, if you are using the .NET, Java, or C++ SDKs, we encourage you to update your application so that you are calling the MapQuest Web Services directly, as the SDKs have been deprecated for quite some time and no future enhancements will be made to these toolkits. The legacy APIs and tools that operate in the Equirectangular map projection were developed long before Web Mercator became the standard map projection for Web mapping applications.  Retiring the systems that power our legacy products will allow us to better focus on the current and next generation of MapQuest APIs and developer tools. We’ve also put together a migration website that contains more information about how to find out what version of a product you are using if you are unsure, more information about the features differences between legacy and current products.  Feel free to visit the Developer Network forum or tweet us @MapQuestTech if you have questions. Note: users of MapQuest Open APIs and developer tools are not affected by the retirement of legacy (licensed) APIs; however, it is always a good idea to ensure that you are using the latest versions of our Open products.