# Introduction to TPS XML API

Source: [https://docs.qualcomm.com/doc/80-42216-1/topic/1_Introduction_to_Qualcomm_TPS_API.html](https://docs.qualcomm.com/doc/80-42216-1/topic/1_Introduction_to_Qualcomm_TPS_API.html)

Qualcomm® Terrestrial Positioning Service (TPS) API, formerly known as
      Skyhook Precision Location API, provides access to positioning information derived from
      analyzing positioning anchors such as Wi-Fi access points and cell IDs in known locations.

Client applications make XML HTTPS requests to the TPS API, which include a list of observed
      beacons used for positioning within the range of the client device, and if available, GPS
      information starting from TPS v2.21. Based on these inputs, the TPS API returns a calculated
      geographic location, and optionally returns a street address and time zone.

In addition to the derived location, the TPS API returns location information based on the IP
      address of the client. While this information is not a reliable source for navigation, it can
      be used to provide context when more accurate methods are not available, and may be used as
      the best estimate of location.

### API limitations

Opting for the API approach has benefits pertaining to server-side features, but is less robust
        than client-side implementations. Few SDK or embedded client features such as smoothing
        between location sources, fast time-to-fix, MAC address deduplication, power optimization,
        and offline location are not available with the API method.

In addition, application or device-specific code must be created to enable the collection of
        Wi-Fi and cell radio scans. For recommendations in these areas to optimize the use of cloud
        API, contact the Qualcomm TPS team at [support.tps@qti.qualcomm.com](mailto:support.tps@qti.qualcomm.com).

### Scope

This document provides an overview of the TPS XML API and its implementation to determine the
        geographic location of connected devices. In addition, the document describes the API
        requests and responses, and provides guidelines to evaluate the API on a large scale.

### Technical assistance

For assistance or clarification, write to [support.tps@qti.qualcomm.com](mailto:support.tps@qti.qualcomm.com).

Last Published: Apr 01, 2026

[Next Topic
TPS XML API headers and authentication](https://docs.qualcomm.com/bundle/publicresource/80-42216-1/topics/2_TPS_XML_API_implementation.md)