Documentation
Reference
2.1.50 (current version)
collection
interactivityModel
Interfaces
2.1.52 (release candidate)
collection
interactivityModel
Interfaces

Terms of use for the API

The Yandex.Maps API is available to anyone who wants to use Yandex maps on a website or in an application.

The API can be used free of charge, or on a commercial basis. Free use is restricted by a number of conditions. The API for Business is intended for commercial use and removes the limitations of the free version. More information about the commercial version.

In this section

Terms of use

Before you begin using the API, review the terms of use:

1. The API may only be used in projects with open access

The free version of the API is intended only for websites and applications that any internet user is allowed to access. If the website or application requires registration, it must be available to anyone. The free version of the API is not intended for projects with restricted access, such as by invitation-only or limited to employees inside a company.

If you need to use the API in restricted-access projects, purchase the API for Business.

2. The API may not be used in commercial projects

The free version of the API is not designed for projects that charge a fee for registration or licensing.

If you want to use the API in a commercial project, purchase the API for Business.

3. Data received via the API must be displayed on the Yandex map

The results of all API requests must be displayed on the Yandex map. For example, this applies to data obtained from the geocoding or routing services.

If you need to use data from the API without displaying it on the map, write to us.

4. Storing or changing data obtained via the API is not allowed

You may not store the data you receive from the API. For example, you aren't allowed to get data from the geocoder once and then store it for later use. Note that you are allowed to cache responses from the geocoder and router for up to 30 days.

You also may not change the data you receive from the API. For example, you aren't allowed to change the ranking of search results or the color scheme of the map base layer.

If you need to store or change data obtained using the API, write to us.

5. It is prohibited to obscure or alter the Yandex copyrights and logos on the map

The Yandex copyright information and logos must always be visible on the map. You are not allowed to move them, cover them up with other elements, obscure them, or alter them in any way. This applies to both interactive and static maps. For this reason, publishing screenshots of maps is not allowed. To get a static image of a map, you can use the Map Constructor or the Static API.

Note that this requirement is also enforced in the commercial version of the API. If you have a reason to obscure the Yandex copyrights or logos in your project, write to us.

6. The API may not be used for monitoring and dispatching

You are not allowed to use the map for real-time tracking of transport locations, or for automatically following a route, like a navigator.

If you want to use the API in a tracking system, purchase the API for Business.

7. The API may not be used in gaming projects

Gaming projects include websites and applications that use the map as part of a game.

If you want to use the API in a game, purchase the API for Business.

8. The daily limit on API requests must not be exceeded

The API has a daily limit on the use of the Yandex geocoding, routing, and panorama services. For the free version of the API, the limit is 25,000 requests per day. For more information about which requests fall under this restriction, see the table below.

If you need to increase your daily limit, purchase the API for Business.

Note. The terms of use for the API are regulated by the User Agreement. This document only explains the points in the agreement.

Limits on API requests

The API has a daily limit on the total number of requests to the Yandex geocoding, routing, and panorama services. The number of requests is calculated using the following formula:

Geocoder requests + Router requests + 5 × Panorama requests

In the free version of the API, the total number of requests must not exceed 25,000 requests per day. In the commercial version, this limit depends on the rate for the purchased license.

The operations listed below send requests to these services, so they count toward the API limit.

ServiceOperation
Geocoding

— Requests to the Geocoder HTTP API.

— Calling the geocode() function.

— Getting a user's location using the geolocation.get() function when reverse geocoding is enabled ('autoReverseGeocode' is set to true).

— Routing when reference points are set as addresses (as in the example). Each address initiates a separate geocoder request.

— Searching on the map using control.SearchControl, when the provider is set as toponym search (the 'provider' option has the value 'yandex#map').

The following operations are not counted:

— Geolocation with reverse geocoding disabled ('autoReverseGeocode' is set to false).

— Searching on the map using control.SearchControl with the 'yandex#search' provider.

Routing

— Calling the route() function.

— Instantiating the multiRouter.MultiRoute class.

— Building a route using the control.RouteEditor control.

— Editing a route: adding, removing, or dragging points*
[no-highlight[

* When dragging route points, requests are sent to the router approximately every three seconds when the server response is fast enough. For the multirouter, you can use the dragUpdateInterval option to increase the interval between requests. If necessary, you can use the preventDragUpdate option to completely disable route updates during editing.

]no-highlight]
.

— Changing router options that require rebuilding a route. Some examples are enabling traffic calculations or changing the type of routing.

Yandex panoramas

— Calling the panorama.locate() function for searching for panoramas near a specified point.

— Calling the panorama.createPlayer() function for creating a panorama player on a page.

The following operations are not counted:

— Switching between connected panoramas in an open panorama player, such as following connection arrows.

— Creating a panorama player with a custom panorama.

— Adding the panorama layer to the map.

— Opening panoramas for clicks on the panorama layer on the map.

* When dragging route points, requests are sent to the router approximately every three seconds when the server response is fast enough. For the multirouter, you can use the dragUpdateInterval option to increase the interval between requests. If necessary, you can use the preventDragUpdate option to completely disable route updates during editing.

Feedback

If you have any questions about the terms of use, please write to us.

Yandex.Maps API documentation
Request limits
Free use of the Yandex.Maps API
Commercial license
Restrictions in the Yandex.Maps API