Reverse geocode to address

POST 
/geocoding/resolve

The Reverse geocoding API uses geocoder backends available to the authenticated user within their accessible projects. By default, all available geocoders across all accessible projects are utilized. Project managers control which geocoders are available to project users.

You can restrict the geocoders used for a request by specifying the following optional JSON keys:

• project_id: Restricts the search to geocoders found within the project identified by this ID.
• project: Restricts the search to geocoders found within the project identified by this external ID.
• geocoder: Restricts the search to the geocoder identified by this code.
• geocoders: Restricts the search to the geocoders listed in this array of codes.

Important Considerations:

• Project Filtering: If you filter by project_id or project, the authenticated user must be a member of that project. Furthermore, the project must have at least one fully configured geocoding provider; otherwise, the API will return an error.
• Geocoder Filtering: If you filter by geocoder or geocoders, the specified geocoder(s) must be among those available to the authenticated user.
• Combined Filtering: If you filter by both project and geocoder(s), the authenticated user must be a member of the specified project, and the project must contain the specified geocoder code(s).

Request

Responses

200

Notice, that the queries list is united by the (lat, lon) exact values, so only one query is evaluated per such a value. Don't rely to the order of the original queries. Find the query result by the query original lat/lon parameters.