Search - Get Reverse Geocoding
Use to get a street address and location info from longitude and latitude coordinates.
The Get Reverse Geocoding API is an HTTP GET request used to translate a coordinate (example: 37.786505, -122.3862) into a human understandable street address. Useful in tracking applications where you receive a GPS feed from the device or asset and wish to know the address associated with the coordinates. This endpoint will return address information for a given coordinate.
GET {endpoint}/reverseGeocode?api-version=2026-01-01&coordinates={coordinates}
GET {endpoint}/reverseGeocode?api-version=2026-01-01&coordinates={coordinates}&resultTypes={resultTypes}&view={view}
URI Parameters
| Name | In | Required | Type | Description |
|---|---|---|---|---|
|
endpoint
|
path | True |
string (uri) |
The Azure Maps service hostname. Use |
|
api-version
|
query | True |
string minLength: 1 |
The API version to use for this operation. |
|
coordinates
|
query | True |
number[] |
The coordinates of the location that you want to reverse geocode. Example: &coordinates=lon,lat |
|
result
|
query |
Specify entity types that you want in the response. Only the types you specify will be returned. If the point cannot be mapped to the entity types you specify, no location information is returned in the response. Default value is all possible entities. A comma separated list of entity types selected from the following options.
These entity types are ordered from the most specific entity to the least specific entity. When entities of more than one entity type are found, only the most specific entity is returned. For example, if you specify Address and AdminDistrict1 as entity types and entities were found for both types, only the Address entity information is returned in the response. |
||
|
view
|
query |
string |
A string that represents an ISO 3166-1 Alpha-2 region/country code. This will alter Geopolitical disputed borders and labels to align with the specified user region. By default, the View parameter is set to "Auto" even if you haven't defined it in the request. Please refer to Supported Views for details and to see the available Views. |
Request Header
| Name | Required | Type | Description |
|---|---|---|---|
| x-ms-client-id |
string |
Specifies which account is intended for usage in conjunction with the Azure AD security model. It represents a unique ID for the Azure Maps account and can be retrieved from the Azure Maps management plane Account API. For more information on using Microsoft Entra ID security in Azure Maps, see Manage authentication in Azure Maps. |
|
| Accept-Language |
string |
Language in which search results should be returned. Please refer to Supported Languages for details. |
Responses
| Name | Type | Description |
|---|---|---|
| 200 OK |
The request has succeeded. Media Types: "application/geo+json", "application/json" |
|
| Other Status Codes |
An unexpected error response. Media Types: "application/geo+json", "application/json" Headers x-ms-error-code: string |
Security
AadToken
These are the Microsoft Entra OAuth 2.0 Flows. When paired with Azure role-based access control it can be used to control access to Azure Maps REST APIs. Azure role-based access controls are used to designate access to one or more Azure Maps resource account or sub-resources. Any user, group, or service principal can be granted access via a built-in role or a custom role composed of one or more permissions to Azure Maps REST APIs.
To implement scenarios, we recommend viewing authentication concepts. In summary, this security definition provides a solution for modeling application(s) via objects capable of access control on specific APIs and scopes.
Note
- This security definition requires the use of the
x-ms-client-idheader to indicate which Azure Maps resource the application is requesting access to. This can be acquired from the Maps management API. - The
Authorization URLis specific to the Azure public cloud instance. Sovereign clouds have unique Authorization URLs and Microsoft Entra ID configurations. - The Azure role-based access control is configured from the Azure management plane via Azure portal, PowerShell, CLI, Azure SDKs, or REST APIs.
- Usage of the Azure Maps Web SDK allows for configuration based setup of an application for multiple use cases.
- For more information on Microsoft identity platform, see Microsoft identity platform overview.
Type:
oauth2
Flow:
implicit
Authorization URL:
https://login.microsoftonline.com/common/oauth2/authorize
Scopes
| Name | Description |
|---|---|
| https://atlas.microsoft.com/.default |
subscription-key
This is a shared key that is provisioned when you Create an Azure Maps account in the Azure portal or using PowerShell, CLI, Azure SDKs, or REST API.
With this key, any application can access all REST API. In other words, this key can be used as a master key in the account that they are issued in.
For publicly exposed applications, our recommendation is to use the confidential client applications approach to access Azure Maps REST APIs so your key can be securely stored.
Type:
apiKey
In:
header
SAS Token
This is a shared access signature token is created from the List SAS operation on the Azure Maps resource through the Azure management plane via Azure portal, PowerShell, CLI, Azure SDKs, or REST APIs.
With this token, any application is authorized to access with Azure role-based access controls and fine-grain control to the expiration, rate, and region(s) of use for the particular token. In other words, the SAS Token can be used to allow applications to control access in a more secured way than the shared key.
For publicly exposed applications, our recommendation is to configure a specific list of allowed origins on the Map account resource to limit rendering abuse and regularly renew the SAS Token.
Type:
apiKey
In:
header
Examples
Search point -122.138681, 47.630358
Sample request
GET https://atlas.microsoft.com/reverseGeocode?api-version=2026-01-01&coordinates=-122.138681,47.630358
Sample response
Content-Type: application/geo+json
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"address": {
"countryRegion": {
"name": "United States"
},
"adminDistricts": [
{
"name": "Washington",
"shortName": "WA"
},
{
"name": "King County",
"shortName": "King Co."
}
],
"formattedAddress": "15127 NE 24th St, Redmond, Washington 98052",
"streetName": "NE 24th St",
"streetNumber": "15127",
"locality": "Redmond",
"postalCode": "98052",
"addressLine": "15127 NE 24th St"
},
"type": "Address",
"confidence": "Medium",
"matchCodes": [
"Good"
],
"geocodePoints": [
{
"geometry": {
"type": "Point",
"coordinates": [
-122.138681,
47.630358
]
},
"calculationMethod": "Rooftop",
"usageTypes": [
"Display"
]
},
{
"geometry": {
"type": "Point",
"coordinates": [
-122.1386787,
47.6302179
]
},
"calculationMethod": "Rooftop",
"usageTypes": [
"Route"
]
}
]
},
"geometry": {
"type": "Point",
"coordinates": [
-122.138681,
47.630358
]
},
"bbox": [
-122.14632282407,
47.626495282429325,
-122.13103917593001,
47.63422071757068
]
}
]
}
Definitions
| Name | Description |
|---|---|
| Address |
The address of a geocoded or autocomplete-suggested location, parsed into structured fields.
Sparseness is normal: only the fields that the resolved entity supplies are populated. For
example, |
|
Address |
An administrative subdivision that contains an address. For example, a state, province, or
county. Returned as one entry in the parent |
|
Address |
The country or region that contains the address, identified by its display name and ISO 3166-1 Alpha-2 country code. Either field may be omitted in a given response. |
|
Azure. |
The error object. |
|
Azure. |
A response containing error details. |
|
Azure. |
An object containing more specific information about the error. As per Azure REST API guidelines - https://aka.ms/AzureRestApiGuidelines#handling-errors. |
|
Calculation |
The method that was used to compute the geocode point. |
|
Confidence |
The level of confidence that the geocoded location result is a match. Use this value together with the match codes to obtain more complete information about the match. The confidence of a geocoded location is based on many factors, including the relative importance of the geocoded location and the user's location, if specified. |
|
Feature |
The |
|
Features |
A single entry in the |
|
Features |
The |
|
Feature |
The |
|
Geocode |
One geocode point for a location: a coordinate plus metadata describing how the point was
computed ( |
|
Geocoding |
The successful response body returned by |
|
Geo |
Specifies the |
|
Geo |
A valid |
| Intersection |
Intersection details for an address resolved as a road intersection — the corner where two or
more named streets meet. Populated only when the resolved entity is a |
|
Match |
A match-code value indicating how the geocoding service produced a particular location
result. The |
|
Reverse |
An entity type returned by the |
|
Usage |
The intended use for a geocode point. A geocode point returned by the service carries one or more usage types that indicate how a client application should consume the point: for example, displaying the location on a map versus routing a vehicle to it. |
Address
The address of a geocoded or autocomplete-suggested location, parsed into structured fields.
Sparseness is normal: only the fields that the resolved entity supplies are populated. For
example, streetName and streetNumber appear only for street-level addresses, and
intersection appears only for road-intersection results.
| Name | Type | Description |
|---|---|---|
| addressLine |
string |
The first line of the address, typically the street name and number. For example,
|
| adminDistricts |
The administrative subdivisions that contain the address, ordered from coarsest to finest. The first entry is typically the first-order subdivision (such as a U.S. state or a Canadian province); subsequent entries cover finer divisions where the country, dependency, or region defines them (such as a county at index 1). |
|
| countryRegion |
The country or region that contains the address, with its display name and ISO 3166-1 Alpha-2 country code. |
|
| formattedAddress |
string |
The full address rendered as a single human-readable string, with the components joined
according to the conventions of the address's country or region. Example:
|
| intersection |
The intersecting-street details for the address, populated when the resolved entity is a
|
|
| locality |
string |
The locality the address falls within: usually a city, town, or village. For example:
|
| neighborhood |
string |
The named neighborhood within the locality, when one is identified. |
| postalCode |
string |
The postal code for the address, when one is defined. Example: |
| streetName |
string |
The street name component of the address, when the resolved entity is a street-level
address. Example: |
| streetNumber |
string |
The house or building number on the street, when the resolved entity is a street-level
address. Example: |
AddressAdminDistrictsItem
An administrative subdivision that contains an address. For example, a state, province, or
county. Returned as one entry in the parent Address.adminDistricts array, where entries are
ordered from coarsest to finest.
| Name | Type | Description |
|---|---|---|
| name |
string |
The full name of the subdivision. For example, |
| shortName |
string |
The short or abbreviated form of the subdivision name, when one is defined. For example,
|
AddressCountryRegion
The country or region that contains the address, identified by its display name and ISO 3166-1 Alpha-2 country code. Either field may be omitted in a given response.
| Name | Type | Description |
|---|---|---|
| ISO |
string |
The ISO 3166-1 Alpha-2 country code for the country or region. For example, |
| name |
string |
The display name of the country or region. For example, |
Azure.Core.Foundations.Error
The error object.
| Name | Type | Description |
|---|---|---|
| code |
string |
One of a server-defined set of error codes. |
| details |
An array of details about specific errors that led to this reported error. |
|
| innererror |
An object containing more specific information than the current object about the error. |
|
| message |
string |
A human-readable representation of the error. |
| target |
string |
The target of the error. |
Azure.Core.Foundations.ErrorResponse
A response containing error details.
| Name | Type | Description |
|---|---|---|
| error |
The error object. |
Azure.Core.Foundations.InnerError
An object containing more specific information about the error. As per Azure REST API guidelines - https://aka.ms/AzureRestApiGuidelines#handling-errors.
| Name | Type | Description |
|---|---|---|
| code |
string |
One of a server-defined set of error codes. |
| innererror |
Inner error. |
CalculationMethodEnum
The method that was used to compute the geocode point.
| Value | Description |
|---|---|
| Interpolation |
The geocode point was matched to a point on a road using interpolation. |
| InterpolationOffset |
The geocode point was matched to a point on a road using interpolation with an additional offset to shift the point to the side of the street. |
| Parcel |
The geocode point was matched to the center of a parcel. |
| Rooftop |
The geocode point was matched to the rooftop of a building. |
ConfidenceEnum
The level of confidence that the geocoded location result is a match. Use this value together with the match codes to obtain more complete information about the match.
The confidence of a geocoded location is based on many factors, including the relative importance of the geocoded location and the user's location, if specified.
| Value | Description |
|---|---|
| High |
If the confidence is set to If a request includes a location or a view, then the ranking may change accordingly. For
example, a location query for "Paris" returns both "Paris, France" and "Paris, TX" with
|
| Medium |
In some situations, the returned match may not be at the same level as the information
provided in the request. For example, a request may specify address information and the
geocode service may only be able to match a postal code. In this case, if the geocode
service has confidence that the postal code matches the data, the confidence is set to
If the location information in the query is ambiguous, and there is no additional information
to rank the locations (such as user location or the relative importance of the location), the
confidence is set to If the location information in the query does not provide enough information to geocode a
specific location, a less precise location value may be returned and the confidence is set to
|
| Low |
Low confidence in the match. |
FeatureCollectionEnum
The GeoJSON object type used at the root of successful responses from the forward
geocoding, reverse geocoding, and autocomplete operations (including their batch
variants). The only value is FeatureCollection, as defined in
RFC 7946. Get Polygon is the one exception:
its response root is a GeoJSON Feature, see FeatureTypeEnum.
| Value | Description |
|---|---|
| FeatureCollection |
The |
FeaturesItem
A single entry in the features array of a GeocodingResponse, conforming to the
GeoJSON Feature object shape.
Represents one geocoded location: structured data on properties, a representative
coordinate on geometry, and an optional bounding box on bbox.
| Name | Type | Description |
|---|---|---|
| bbox |
number[] (double) |
The smallest axis-aligned rectangle that contains the feature's geometry, in WGS 84
longitude/latitude order. Encoded as |
| geometry |
The primary |
|
| id |
string |
An optional service-assigned identifier for the feature, when one is available. |
| properties |
Structured data about the geocoded location, including its entity type, match-quality indicators, address components, and one or more geocode points. |
|
| type |
The |
FeaturesItemProperties
The properties payload of a feature in a GeocodingResponse. Carries the entity type and
match-quality indicators for the geocoded location, its parsed address components, and one or
more geocode points that pin the location to specific coordinates.
| Name | Type | Description |
|---|---|---|
| address |
The address of the geocoded location, parsed into structured fields such as locality, postal code, country/region, and (when available) street name and number. |
|
| confidence |
How strongly the geocoded location matches the request. Use together with |
|
| geocodePoints |
One or more geocode points for the location, each marked with how it was derived
( |
|
| matchCodes |
How the geocoding service produced this result relative to the query: a direct match at the
requested specificity ( |
|
| type |
string |
The entity type that the geocoded location resolved to. One of: |
FeatureTypeEnum
The GeoJSON object type for Feature objects. Tags each entry inside the features
array of a FeatureCollection response (geocoding, reverse geocoding, autocomplete) and
appears at the root of the Get Polygon response. The only value is Feature, as
defined in RFC 7946.
| Value | Description |
|---|---|
| Feature |
The |
GeocodePointsItem
One geocode point for a location: a coordinate plus metadata describing how the point was
computed (calculationMethod) and what it is best suited for (usageTypes). A single feature
typically returns separate Display and Route points so callers can pick the one that fits
the task.
| Name | Type | Description |
|---|---|---|
| calculationMethod |
How the point was computed. For example, snapped to the rooftop of a building or
interpolated along a road centerline. See |
|
| geometry |
The coordinate of this geocode point as a
|
|
| usageTypes |
What the geocode point is best suited for — |
GeocodingResponse
The successful response body returned by Get Geocoding and Get Reverse Geocoding, and
the per-batch-item success shape carried inside GeocodingBatchResponse.batchItems.
Encoded as a GeoJSON FeatureCollection whose
features array contains one Feature per geocoded location.
| Name | Type | Description |
|---|---|---|
| features |
The array of |
|
| nextLink |
string |
Contains the URL to fetch the next page of results if the response is paginated. This is useful when the response is too large to be returned in a single call, allowing users to navigate through multiple pages of results. |
| type |
The |
GeoJsonObjectType
Specifies the GeoJSON type. Must be one of the nine valid GeoJSON object
types - Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon,
GeometryCollection, Feature and FeatureCollection.
| Value | Description |
|---|---|
| Point |
|
| MultiPoint |
|
| LineString |
|
| MultiLineString |
|
| Polygon |
|
| MultiPolygon |
|
| GeometryCollection |
|
| Feature |
|
| FeatureCollection |
|
GeoJsonPoint
A valid GeoJSON Point geometry type. Please refer to RFC
7946 for details.
| Name | Type | Description |
|---|---|---|
| bbox |
number[] (double) |
Bounding box. Projection used - EPSG:3857. Please refer to RFC 7946 for details. |
| coordinates |
number[] (double) |
A |
| type |
string:
Point |
Specifies the |
Intersection
Intersection details for an address resolved as a road intersection — the corner where two or
more named streets meet. Populated only when the resolved entity is a RoadIntersection; the
parent Address.intersection is otherwise omitted.
| Name | Type | Description |
|---|---|---|
| baseStreet |
string |
The primary street of the intersection — typically the street the address number references. |
| displayName |
string |
A human-readable name for the intersection that combines the cross streets, such as
|
| intersectionType |
string |
A short label describing the form of the intersection. For example, distinguishing an at-grade crossroads from a grade-separated crossing such as a bridge or overpass. |
| secondaryStreet1 |
string |
The first cross street that meets |
| secondaryStreet2 |
string |
The second cross street at the intersection, when one is present. Populated only for intersections of three or more streets. |
MatchCodesEnum
A match-code value indicating how the geocoding service produced a particular location
result. The matchCodes field on a feature is an array of these values; combine them with
confidence and type to evaluate match quality.
| Value | Description |
|---|---|
| Good |
The geocoding service produced this candidate without broadening the query: the result matches the query at the specificity that was requested. |
| Ambiguous |
The location is one of a set of possible matches. For example, when querying for the street address "128 Main St.", the response may return two locations for "128 North Main St." and "128 South Main St." because there is not enough information to determine which option to choose. |
| UpHierarchy |
The location represents a move up the geographic hierarchy. This occurs when a match for the location request was not found, so a less precise result is returned. |
ReverseGeocodingResultTypeEnum
An entity type returned by the Get Reverse Geocoding operation. Supplied as one or more
values in the resultTypes query parameter to restrict the response to specific kinds of
locations; when the parameter is omitted, all entity types are eligible. When entities of
more than one type match a coordinate, only the most specific is returned. Listed from
most specific to least specific: Address, Neighborhood, PopulatedPlace, Postcode1,
AdminDivision1, AdminDivision2, CountryRegion.
| Value | Description |
|---|---|
| Address |
A specific street address. |
| Neighborhood |
A locally recognized area within a populated place, often with informal or culturally defined boundaries. |
| PopulatedPlace |
A concentrated area of human settlement, such as a city, town or village. |
| Postcode1 |
The smallest postal code category, such as a zip code. |
| AdminDivision1 |
First administrative level within the country/region, such as a state or a province. |
| AdminDivision2 |
Second administrative level within the country/region, such as a county. |
| CountryRegion |
A country or region. |
UsageTypeEnum
The intended use for a geocode point. A geocode point returned by the service carries one or more usage types that indicate how a client application should consume the point: for example, displaying the location on a map versus routing a vehicle to it.
| Value | Description |
|---|---|
| Display |
The geocode point is suitable for displaying the location on a map. For a feature with
non-trivial extent (such as a park or building), the |
| Route |
The geocode point is suitable as the destination of a route. For a feature with
non-trivial extent (such as a park or building), the |