# Forward location response using Echo

Source: [https://docs.qualcomm.com/doc/80-42204-1/topic/25_TPS_JSON_API_for_IoT__Echo_.html](https://docs.qualcomm.com/doc/80-42204-1/topic/25_TPS_JSON_API_for_IoT__Echo_.html)

Echo is a key feature developed specifically for IoT as a mechanism to forward location
                information of devices in real time directly from the positioning server to the OEM
                web server. This feature allows mapping and tracing applications to display the
                location of a device without the need for additional round-trip communication to the
                device.

### Implementation of Echo

Note: Contact the Qualcomm Terrestrial Positioning Service (TPS) team at [support.tps@qti.qualcomm.com](mailto:support.tps@qti.qualcomm.com) to set up and configure Echo.

The client application provides the URL to the remote server. The service uses HTTP
                authentication, a username and password generated by Qualcomm, for securing the
                traffic. After the URL is confirmed, the username and password are relayed to the
                client application. The URL and credentials are provided to the OEM via a secure
                means of communication of their choice.

### Sample JSON POST message

    {
      "location": {
        "lat": 40.071248,
        "lon": -75.465249
      },
      "accuracy": 5,
      "source": "WIFI",
      "status": "SUCCESS",
      "partner_id": "12345",
      "device_id": "4aa472471972"
    }Copy to clipboard

### Parameters

| Parameter | Values | Description |
| --- | --- | --- |
| `accuracy` | <ul class="ul" id="TPS_JSON_API_for_IoT__Echo__25__ul_dxq_nsn_myb_kelvinb_08-18-23-1523-41-473"><br>                                    <li class="li">68% (default)</li><br><br>                                    <li class="li">95%</li><br><br>                                </ul> | Estimated horizontal positioning error (HPE) of the location, in meters when<br>                                    `hpeConfidence` is set to the value mentioned in<br>                                the request.<br>Note: The default 68% confidence<br>                                    is supported in TPS v2.28 and later. For 95% confidence, set<br>                                        `hpeConfidence` to 95 in the location<br>                                    request. |
| `source` | <ul class="ul" id="TPS_JSON_API_for_IoT__Echo__25__ul_lhg_ysn_myb_kelvinb_08-18-23-1526-47-641"><br>                                    <li class="li">Unknown</li><br><br>                                    <li class="li">cell</li><br><br>                                    <li class="li">wifi</li><br><br>                                    <li class="li">gnss</li><br><br>                                    <li class="li">ble</li><br><br>                                    <li class="li">rfpm</li><br><br>                                    <li class="li">hybrid (scans of multiple beacon types used)</li><br><br>                                </ul> | The beacon type that was used to determine the location.<br>This value is populated only when<br>                                        ` includeLocationSource = true` in the<br>                                    request. |
| `status` | <ul class="ul" id="TPS_JSON_API_for_IoT__Echo__25__ul_hkk_vsn_myb_kelvinb_08-18-23-1525-57-691"><br>                                    <li class="li">200 (successful)</li><br><br>                                    <li class="li">400 (failed)</li><br><br>                                </ul> | Status of the response. |
| `partner_id` | – | API-Advanced Encryption Standard (AES) key created for the project. |
| `device_id` | – | End-user device identification number provided in the location request. |

Last Published: Mar 17, 2026

[Previous Topic
Token-based registration](https://docs.qualcomm.com/bundle/publicresource/80-42204-1/topics/24_Token_based_registration_using_a_license.md) [Next Topic
Evaluate TPS JSON API](https://docs.qualcomm.com/bundle/publicresource/80-42204-1/topics/26_Guidelines_to_evaluate_TPS_JSON_API.md)