Mapy Developers Updates & Release Notes

We’ve prepared new testing labs for working with geocoding and routing API functions.

The labs are designed for quick testing of API endpoints, their parameters, and responses. Developers can easily verify how functions behave without needing to implement their own integration.

The new labs replace the previous version and bring several improvements:

• cleaner and more modern UI
• easier parameter setup (both via text input and directly from the map)
• better visualization of results and constraints on the map
• ability to paste an existing REST URL and debug it
• overall improved user experience

Geocoding lab:

https://pro.mapy.com/examples/geocode/

Allows you to test geocoding, reverse geocoding, and autocomplete.

Routing lab:

https://pro.mapy.com/examples/route/

Allows you to plan routes between multiple waypoints and test different routing options.

We have expanded the route-planning function in the Mapy.com REST API. The changes are based on frequent feedback from our users.

We are not breaking backward compatibility — the existing interface and behavior remain unchanged, we are only adding new input and output parameters. No adjustments to current integrations are required.

New input parameters

• avoidHighways

  In addition to the existing avoidToll parameter (avoid toll roads), we are introducing avoidHighways, which allows route planning to avoid highways / express roads.

• departure

  Optional departure time in local time (ISO-8601, e.g. 2025-01-01T00:00:00.000). If not provided, planning uses “now”. This parameter affects time-dependent restrictions (closures, traffic limits, etc.).

New output parameters

• parts

  An array of route segments between the start, optional waypoints, and destination. Each segment includes its own length (in meters) and duration (in seconds).

• routePoints

  An array with detailed information about the start, destination, and waypoints after snapping to the routing network.
  Values originalPosition, mappedPosition, and snapDistance describe the shift to the nearest routable edge.
  If restricted = true, the point lies in an area that would normally be excluded from routing (e.g., a limited-access or non-routable area), but the route was still calculated because the point was explicitly specified as start, end, or waypoint. The restrictionType attribute specifies the reason.

To simplify working with our REST API, we have now made the documentation available on GitHub as well: github.com/mapycom/developer. This documentation is provided as standalone Markdown (.md) files. This format is useful, among other things, for leveraging the modern development approach called vibe coding, where instead of writing code, you simply describe the application using an AI prompt.

Since AI models may not know the details of our continuously updated API, it is necessary to give them the current context to generate correct and functional code. Just attach the appropriate .md files from our repository to your AI prompt (such as Gemini, ChatGPT or Copilot). For example, to work with the map, attach map-tiles.md; for route planning, attach routing.md. Thanks to this, you can obtain a functional application prototype within a few minutes, even without deep programming knowledge.

You can find a detailed guide to this method in the article Vibe coding with the Mapy.com REST API.

We are adding a new option to the Mapy.com REST API for planning walking routes.

Until now, the REST API Routing function offered the walking – fast (foot_fast) option, which always searched for the fastest (and usually the shortest) path.

We are now introducing the hiking (foot_hiking) option. When used, the API will find a route that may not be the shortest but will prefer marked hiking trails and more interesting walking paths.

This option is ideal for planning trips, hikes, and walking routes – situations where the goal is not to arrive as quickly as possible but to enjoy the journey itself.

Your September invoice comes with good news – we are introducing automatic discounts on paid credits.

Previously, getting a discount was quite complicated: you had to reach and maintain high usage, contact a sales representative, and sign a tailored contract. Now, we’ve simplified the entire process. Discounts are applied automatically for all users of the Basic and Extended Tariffs.

➡️ You can try out the new discounts anytime in our pricing calculator.

If your paid usage exceeds 5 million credits, the base price will gradually decrease according to defined tiers. Everything happens automatically.

How it works

The mechanism is based on cumulative tiered billing:

• free credits (according to your tariff) are consumed first
• the remaining paid usage is then split into tiers with different prices.

Example

Usage of 17 million credits in the Extended tariff:

• 10 mil. credits are free,
• 5 mil. × 1.6 CZK / 1,000 = 8,000 CZK,
• 2 mil. × 1.1 CZK / 1,000 = 2,200 CZK.

Total with automatic discounts: 10,200 CZK.

For comparison (previous model): 7 mil. × 1.6 CZK / 1,000 = 11,200 CZK.

Savings: 1,000 CZK.

Discount tiers

From To Price per 1,000 credits

0 5,000,000 1.6 CZK – base price

5,000,000 10,000,000 1.1 CZK

10,000,000 20,000,000 0.8 CZK

20,000,000 35,000,000 0.6 CZK

35,000,000 50,000,000 0.4 CZK

50,000,000 100,000,000 0.3 CZK

100,000,000 above 100,000,000 0.2 CZK

We have added over one billion missing buildings worldwide to our map base.

Buildings are a crucial element for orientation in both urban areas and open landscapes, where individual structures often serve as prominent landmarks.

The data was sourced from a combination of global and local providers, including qualified satellite imagery, covering densely populated regions as well as previously overlooked locations.

These updates are already live in the Mapy API and tile services.

Take a look at the attached image to see the before and after.

What is changing and what stays the same

In recent months, Mapy.cz has transitioned to a new domain and brand: Mapy.com. Now, starting from June 1, 2025, this change also applies to developer services: the REST API Mapy.cz is being renamed to REST API Mapy.com, and the developer portal is officially moving to developer.mapy.com.

No changes are required in existing applications. All current endpoints and URLs will continue to work.

Technical aspects:

• No changes are required in existing applications – all endpoints on the api.mapy.cz domain remain fully functional.
• The REST API will also be newly available on the api.mapy.com domain; we recommend using the .com addresses for new integrations.
• Mapy.com URLs will continue to work in the format mapy.cz/fnc/… as well as the new format mapy.com/fnc/….

Documentation and portal:

• The developer portal will now only be available at developer.mapy.com.
• The API project management portal will be available at developer.mapy.com/account.

New terms and conditions

In connection with the service renaming, there is an update to the terms and conditions, which will come into effect on June 1, 2025.

Main changes:

• These are primarily formal changes – renaming the service from REST API Mapy.cz to REST API Mapy.com.
• A minor new condition applies to the Discounted Plan: projects using this plan must be published in the reference project catalog. (Most projects already meet this condition.)

If you have any questions or need help with setting up a new integration, please contact us via the contact form.