# TPS user beacon API headers and authentication

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

The Terrestrial Positioning Service (TPS) user beacon API corrects the geographic
            location that has been previously reported by a Location call. This API call corrects
            the known position of the access points and cell towers so that subsequent Location
            calls are placed at the location provided by the user.

There is no validation performed on the location provided by the user. If an incorrect
            location is provided, then the Location call will be equally inaccurate. A TPS user
            beacon API call overrides any previous calls, and corrects the access points and
            position of cell towers to the latest location submitted by the user.

## API key

An evaluation license agreement is required to obtain an API key for TPS. For more
                information about the license agreement, contact the Qualcomm TPS team at [sales.tps@qti.qualcomm.com](mailto:sales.tps@qti.qualcomm.com).

## Unique device ID

With each unique location request, it's recommended to submit a unique device ID or
                    `user` for the end-user device. This enables more accurate
                location results and impacts the redundancy of how location data is processed and
                weighted for optimization. If `user` isn't provided, reporting and
                API performance may be impacted.

Note: Individual device IDs aren't stored permanently in
                Qualcomm’s system, but are stored with a rotating hash in accordance with Qualcomm
                user and commercial privacy policies.

## Endpoint URL

The TPS user beacon API endpoint URL of JSON-formatted requests is [https://global.skyhook.com/wps2/json/user-beacon](https://global.skyhook.com/wps2/json/user-beacon).

## HTTP authentication methods

The TPS user beacon API request can be authenticated using:
- **HTTP headers**: Provide the authorized key in the
                            `Skyhook-Auth-Key` header and the username associated
                        with the key in `Skyhook-Auth-User`.
- **HTTP URL parameters**: Provide the authorized key and username
                        associated with the key at the end of the user beacon API endpoint URL.

        https://global.skyhook.com/wps2/json/user-beacon?key="<API KEY>&user=<USERNAME>"Copy to clipboard

Last Published: Jul 03, 2026

[Previous Topic
Introduction to TPS user beacon API](https://docs.qualcomm.com/bundle/publicresource/80-42223-1/topics/introduction_to_tps_user_beacon_api.md) [Next Topic
TPS user beacon API request](https://docs.qualcomm.com/bundle/publicresource/80-42223-1/topics/user_beacon_api_request.md)