Sorry, you need to enable JavaScript to visit this website.

CrossStreet lookup

 

Service version: 2.0
Last edit: 2019.02.01

On this page

Purpose

This endpoint will return address information for a position.

  • There may be times when you need to translate a coordinate (for example: 37.786505, -122.3862) into a human understandable street address.
  • Most often this is needed in tracking applications where you receive a GPS feed from the device or an asset, and wish to know the address where the point is located.

Run this endpoint

You can easily run this and other endpoints.

  1. Go to the TomTom API Explorer page.
  2. Click an endpoint.
    1. Click Try it out.
    2. Enter/select all required parameter values and any optional parameter values.
    3. At the bottom of the form, click Execute.
    4. Review the Response.

Request data

HTTPS Method: GET

URL format

For identification purposes:

  • Required constants and parameters are shown in bold text.
  • Optional parameters are shown in plain text.
https://api.tomtom.com/search/2/reverseGeocode/crossStreet/37.8328,-122.27669.json?key=*****limit=1&spatialKeys=true&heading=0&radius=1000&language=en-us

curl command

curl -X GET "https://api.tomtom.com/search/2/reverseGeocode/crossStreet/37.8328,-122.27669.json?&key=*****
  &limit=1
  &spatialKeys=true
  &heading=0
  &radius=1000
  &language=en-us"
-H "accept: */*"

▲ Return to Top

Request parameters

The following data table describes the parameters that can be used in a request.

  • Required parameters must be used or the call will fail.
  • Optional parameters may be used.
  • A parameter's data type is beneath its name.
  • If there is a default value that will be assumed when an optional parameter is not used, it is shown in the table.
  • The order of request parameters is not important.
Required parameters
Parameter Description
baseURL
string
The base URL for calling the API.
Value: api.tomtom.com
versionNumber
integer
The service version number.
Value: The current version number value is 2.
position
string
This is specified as a comma separated string composed by lat., lon. (e.g., 37.337,-121.89).
Value: A comma separated string composed by lat., lon.
ext
string
Valid response formats.
Values: JSON, JSONP, JS, or XML.
key
string
An API Key valid for the requested service.
Value: Your valid API Key.
Optional parameters
Parameter Description
limit
integer
The maximum number of responses that will be returned.
Default value: 10
Maximum value: 100
spatialKeys
boolean
Deprecated
If the spatialKeys flag is set, the response will also contain the proprietary geo-spatial key information for a specified location.
Default value: false
March 1, 2018:

  • The spatialKeys parameter has been deprecated and will be withdrawn following a 12 month deprecation period.
  • The planned withdrawal date is March 1, 2019.
  • Following withdrawal, API requests that include the spatialKeys parameter will receive a HTTP 400 error in response.
heading
float
The directional heading of the vehicle in degrees, for travel along a segment of roadway.

  • 0 is North, 90 is East, etc.
  • The precision can include up to one decimal place.

Value: Values range from -360 to 360.

radius
integer
The maximum distance in meters from the specified position for the reverseGeocode to consider.
Default value: 10000 meters (10 km).
language
string
The language in which the search results should be returned.

  • Should be one of the supported IETF language tags, case insensitive.
  • When data in a specified language is not available for a specific field, the default language is used.

Default value: NGT
Deprecation notice: Support for no-NO will be removed in favour of no-NB.

▲ Return to top

Response data

Response body

For illustrative purposes the example below is neatly indented and includes all possible Response fields.

  • Actual Responses are more compact and the fields present will vary based on the result type and the data available.
  • See the following Response field section for more information.

When requesting JSON output the Response has the following structure:

{
    "summary": {
        "numResults": 1,
        "queryTime": 176
    },
    "addresses": [],
    "spatialKeys": []
}

Each element of the addresses array is in the following format:

{
    "address": {
        "streetName": "Soquel Dr & Winkle Ave",
        "crossStreet": "Soquel Dr",
        "municipalitySubdivision": "Santa Cruz, Live Oak",
        "municipality": "Santa Cruz, Live Oak",
        "countrySecondarySubdivision": "Santa Cruz",
        "countryTertiarySubdivision": "Santa Cruz",
        "countrySubdivision": "CA",
        "postalCode": "95065",
        "countryCode": "US",
        "country": "United States Of America",
        "countryCodeISO3": "USA",
        "freeformAddress": "Soquel Dr & Winkle Ave, Santa Cruz, CA 95065",
        "countrySubdivisionName": "California",
        "street": "Winkle Ave"
    },
    "position": "36.9882,-121.97511"
}

Each element of the spatialKeys[] array is in the following format:

{
    "priority": "0",
    "val": "1563238492"
}

▲ Return to top

Response fields

The following tables describe all of the fields that can appear in a Response. Fields are listed by the Response section they belong to, and in the order that they appear in the Response.

Primary fields
Field Description
summary{}
object
Summary information about the search that was performed.
addresses[]
array
Result list, sorted in descending order by score.
spatialKeys[]
array
Proprietary geo-spatial key information for a specified location.
summary{} object
Field Description
queryTime
integer
Time spent on resolving the query.
numResults
integer
The number of Results in the response.
addresses[] array
Field Description
address
string
The structured address for the Result.
position
double (LatLon)
The position of the Result.
address{} object
Field Description
streetName
string
The street name.
crossStreet
string
The street being crossed.
municipalitySubdivision
string
Sub / Super City
municipality
string
City / Town
countrySecondarySubdivision
string
County
countryTertiarySubdivision
string
Named Area.
countrySubdivision
string
State or Province
postalCode
string
Postal Code / Zip Code
countryCode
string
Country
country
string
Country name
countryCodeISO3
string
ISO alpha-3 country code
freeformAddress
string
An address line formatted according to the formatting rules of a Result's country of origin, or in case of countries, its full country name.
countrySubdivisionName
string
A full name of the first level of a country administrative hierarchy.

  • This field appears only in case countrySubdivision is presented in an abbreviated form.
  • Supported only for USA, Canada, and Great Britain.
street
string
The street name.
spatialKeys[] array
Field Description
priority
string
Proprietary geo-spatial key information for a specified location.
val
string
Proprietary geo-spatial key information for a specified location.

▲ Return to top

HTTP Response codes

The following table contains Response codes signifying successful and failed requests to an API server.

Code Meaning & possible causes
200 OK: The search successfully returned zero or more results.
400 Bad Request: One or more parameters were incorrectly specified.
403 Forbidden: Possible causes include:

  • Service requires SSL
  • Not authorized
  • Rate or volume limit exceeded
  • Unknown referer
405 Method Not Allowed: The HTTP method (GET, POST, etc) is not supported for this Request.
404/596 Not Found: The HTTP Request method (GET, POST, etc) or path is incorrect.
5xx Server Error: The service was unable to process your Request. Contact support to resolve the issue.

▲ Return to top

Response headers

The following table contains Response headers sent back from an API server.

Header Description
Access-Control-Allow-Origin Ensures that clients implementing the CORS security model are able to access the response from this service.
Value: *
Content-Type Indicates the format of the response, as chosen by the client.
Format: type/subtype; charset=utf-8
Value: type/subtype is one of:

  • application/json
  • text/javascript
  • text/xml

▲ Return to Top