# Location service endpoint

Source: [https://docs.qualcomm.com/doc/80-63441-4/topic/LaaS-location-service.html](https://docs.qualcomm.com/doc/80-63441-4/topic/LaaS-location-service.html)

| Description | Enables the Customer MCU/Cloud to send encrypted location measurements to the<br>                  Qualcomm Aware Cloud. Qualcomm Aware Cloud computes the device location using the<br>                  provided measurements. The computed location is returned back in the HTTP<br>                  response. |
| --- | --- |
| URI | /laas/v1/location |
| Method | POST |
| Protocol | HTTP/1.1 |

## Request header

| Name | Description | Schema |
| --- | --- | --- |
| Authorization\* | Client API Key | String |
| X-QCOM-DSN\* | Device Serial Number | String |
| X-QCOM-TokenType\* | Used for authentication purpose. Set to `apikey` for current<br>                  release | String |
| X-QCOM-ClientType\* | OEM defined client type, such as `web`,<br>                    `mobile`. | String |
| X-QCOM-AppName | OEM defined application name, such as `laas`,<br>                    `aware`. | String |
| X-QCOM-TracingID | OEM defined Tracing ID | String |
| Content-Type\* | application/octet-stream | Binary |

Note: **\*** denotes mandatory fields

The application content is the Location Service request response that is returned from
          `AT$QCLOC?` AT command from the mass market Aware Device. For more
        information, see [AT$QCRLC](https://docs.qualcomm.com/doc/80-63441-4/topic/AT-QCRLC.html).

## Successful responses header 

| Name | Description | Schema |
| --- | --- | --- |
| X-QCOM-DSN | Device Serial Number | String |
| X-QCOM-ASN | Aware Serial Number | String |
| Content-Type | application/json | LocationResponse |

## LocationResponse structure

| Name | Description | Schema |
| --- | --- | --- |
| location | Device Location | Location |
| accuracy | Location accuracy in meters, based on 68% confidence level (such as<br>                    `CEP68`) | double |
| timestamp | Time when location was recorded. Represented as time since UNIX Epoch in<br>                  millisecond | uint64 |

## Location structure

| Name | Description | Schema |
| --- | --- | --- |
| latitude | Latitude | double |
| longitude | Longitude | double |

**Example**

    {
     "location": {
      "latitude": 37.37278,
      "longitude": -121.92654
     },
     "accuracy": 45.6,
     "timestamp": 1707362772059
    }
    Copy to clipboard

## Error responses header

| Name | Description | Schema |
| --- | --- | --- |
| error | Error | String |
| errorMsg | Error Message | String |
| errorDescription | Error Description | String |
| errorCode | Error Code, see [REST API error codes](https://docs.qualcomm.com/doc/80-63441-4/topic/LaaS-REST-API-error-codes.html) | String |

**Example**

    {
     "error": "invalid_request",
     "errorMsg": "Bad Request",
     "errorDescription": "Cause: Invalid/Malformed request",
     "errorCode": "400"
    }
    Copy to clipboard

**Parent Topic:** [Cloud endpoints](https://docs.qualcomm.com/doc/80-63441-4/topic/LaaS-cloud-endpoints.html)

Last Published: Jul 16, 2025

[Previous Topic
Cloud endpoints](https://docs.qualcomm.com/bundle/publicresource/80-63441-4/topics/LaaS-cloud-endpoints.md) [Next Topic
Configuration service endpoint](https://docs.qualcomm.com/bundle/publicresource/80-63441-4/topics/LaaS-config-service.md)