Geocoder API
This API can determine the coordinates of a toponym using its address, or the address of a point using its coordinates.
Before using the Geocoder API, it is recommended to read the terms of use.
Note
You can find out how to use JavaScript API geocoding in the section Search on map of the JavaScript API documentation.
Forward geocoding
Forward geocoding is used for determining an object's coordinates based on its name or address. The API presumes common typos and offers a number of suitable options. For example, you can convert a user-defined address to coordinates.
Reverse geocoding
Reverse geocoding is used for determining an object's address based on its coordinates. For example, you can select the house closest to the point on the map and get its name. For reverse geocoding, you can select the necessary type of toponym. For example, you can search for streets or localities only.
Alert
Systems that send requests to the Geocoder must support the SNI (Server Name Identification) extension of the TLS protocol.
API request limits
The following limits are set for the JavaScript API and Geocoder HTTP API:
-
Requests per second (RPS): Up to 50. It's calculated as the sum of requests from the client and from the server.
-
Total number of requests. The total number of requests is calculated using this formula:
Geocoder requests + Router requests + (5 × Panorama requests)
Alert
In the free version, the total number of requests may not exceed 25,000 per day, of which the number of requests to the Geocoder HTTP API may not exceed 1000 per day. If you exceed the limit set for the JavaScript API or Geocoder HTTP API, you should switch to the commercial version of the API where this limit is set depending on the pricing plan.