# TPS XML API response
Source: [https://docs.qualcomm.com/doc/80-42216-1/topic/19_TPS_XML_API_response.html](https://docs.qualcomm.com/doc/80-42216-1/topic/19_TPS_XML_API_response.html)
The Terrestrial Positioning Service (TPS) XML API response includes latitude, longitude, and HPE
(accuracy) that are determined from the TPS XML API request inputs.
Note: Qualcomm
Technologies, Inc. (QTI) uses multiple methods and sources for positioning IPs.
Hence, HPE may not be returned in all responses.
### Syntax
Response messages are defined by the following syntax:
##.## ##.## ##
Copy to clipboard
### Parameters
| Parameter | Parameter | Parameter | Description |
| --- | --- | --- | --- |
| `version` | `version` | `version` | The version of the API being used. |
| `rqtime` | `rqtime` | `rqtime` | The time at which the XML API request was sent. This value is a
reflection of the value provided in the request. |
| `age` | `age` | `age` | Relative age of the location, in milliseconds or
timestamp. |
| `ncell` | `ncell` | `ncell` | Number of cell towers sent in the request known to the server. |
| `nlac` | `nlac` | `nlac` | Number of Location Area Codes (LACs) sent in the request known to
the server. |
| `lap` | `lap` | `lap` | Age of the youngest access point used to determine the
location. |
| `nap` | `nap` | `nap` | Number of access points sent in the request known to the
server. |
| `nsat` | `nsat` | `nsat` | Number of satellites used to compute the GPS location supplied by
the client, if such information was used to determine
location. |
| `nble` | `nble` | `nble` | Number of BLE beacons sent in the request known to the server.
This parameter is available in TPS v2.31 and later versions. |
| `location-source` | `location-source` | `location-source` | Source of the location.
Possible values are:
unknown
cell
wifi
gnss
ble
rfpm
hybrid (scans of multiple beacon types
used)
This parameter is available in TPS v2.29 and later versions. |
| `latitude` | `latitude` | `latitude` | Calculated physical geographic location, expressed in decimal
degrees using floating point values, using the WGS84 datum. |
| `longitue` | `longitue` | `longitue` | Calculated physical geographic location, expressed in decimal
degrees using floating point values, using the WGS84 datum. |
| `hpe` | `hpe` | `hpe` | Estimates HPE of the location, in meters, when
`hpeConfidence` is set to 68% (default) or 95% in
the API request.
Note: The default 68%
confidence is supported in TPS v2.28 and later. For 95%
confidence, set `hpe-confidence` to 95 in the
location request. |
| `altitude` | `altitude` | `altitude` | Calculated z-axis position of the location, in meters.
This value is returned only if barometric readings are provided
in the request. |
| | | `ref-type` | The reference at which the altitude value is with respect to
WGS84, Above Ground Level (AGL), Mean Sea Level (MSL). |
| | | `vpe` | Vertical Positioning Error (VPE) of the altitude value.
Estimated vertical error of the altitude, in meters, with 68%
confidence. |
| `street-address` | `street-address` | `street-address` | Calculated street position of the location.
A value is returned only if
`street-address-lookup-type` is set to either
`full` or `limited` in the API
request. |
| | `distanceToPoint` | `distanceToPoint` | Distance from the returned location to the address. |
| | `street-number` | `street-number` | Street number of the address. |
| | `address-line` | `address-line` | Contains the street name, and other address lines such as
apartment number, if applicable. |
| | `neighborhood` | `neighborhood` | Neighborhood of the address. |
| | `metro1` | `metro1` | City of the location. |
| | `metro2` | `metro2` | City/township of the location. |
| | `postal-code` | `postal-code` | Postal code associated with the address. |
| | `county` | `county` | County in which the address is located. |
| | `province` | `province` | Province in which the address is located. |
| | `region` | `region` | Region in which the address is located. |
| | `state` | `state` | State in which the address is located. Code is the relevant code
of the state. |
| | `country` | `country` | Country code in which the address is located. Code is the
relevant code of the country. |
| `timezone` | `timezone` | `timezone` | Calculated timezone of the location.
A value is returned only if `timezone-lookup` is
set to `true` in the API request. |
| | `name` | `name` | Name of the time zone. |
| | `tz-offset` | `tz-offset` | UTC offset of the time zone. |
| | `dst-offset` | `dst-offset` | Daylight savings offset of the time zone. |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
### Sample response
35.872346737838.362844212 George Street Sydney Haymarket 2000 New South Wales Australia America/Mexico_City -PT6H PT1H
Copy to clipboard
### Warnings and errors
A partially successful request to the server returns one or more warning messages
with the following syntax:
WARNINGCopy to clipboard
An unsuccessful request to the server returns an error message with the following
syntax:
Unable to determine location
Copy to clipboard
Where:
- `string-with-code` is the textual description of the warning or
error.
- `code` is the numeric code of the warning or error.
Last Published: Apr 01, 2026
[Previous Topic
TPS XML API request](https://docs.qualcomm.com/bundle/publicresource/80-42216-1/topics/4_TPS_XML_API_request.md) [Next Topic
Sample TPS XML API request](https://docs.qualcomm.com/bundle/publicresource/80-42216-1/topics/21_Sample_TPS_XML_API_for_testing.md)