# Configuration service endpoint

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

| Description | Enables the OEM MCU/Cloud to request Aware Cloud for location configurations<br>                  parameters necessary for different positioning technologies. |
| --- | --- |
| URI | /laas/v1/configuration |
| Method | POST |
| Protocol | HTTP/1.1 |

## Request header

| Name | Description | Schema |
| --- | --- | --- |
| Authorization\* | Client API Key; see [Certificate and keys](https://docs.qualcomm.com/doc/80-63441-4/topic/AMM-certs-n-keys.html) | 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 configuration request response that is returned
        from `AT$QCRLC?` AT command from the mass market Aware Device. See [AT$QCRLC](https://docs.qualcomm.com/doc/80-63441-4/topic/AT-QCRLC.html) for more details.

## Successful responses header 

| Name | Description | Schema |
| --- | --- | --- |
| X-QCOM-DSN | Device Serial Number | String |
| X-QCOM-ASN | Aware Serial Number | String |
| Content-Type | application/octet-stream | Binary |

The response content is an octet stream containing encrypted location configurations
        generated by the Qualcomm Aware Cloud. The encrypted data needs to be injected back to the
        Aware Agent on the device using `AT$QCSLC` AT command.

In case of an error, following is returned:

Table :

| Name | Description | Schema |
| --- | --- | --- |
| Error | application json | errorResponse |

The following is the errorResponse structure:

| Name | Description | Schema |
| --- | --- | --- |
| errorCode | Error Code, see Chapter 5.4 | String |
| errorMessage | Error Message | String |
| errorDescription | Error Description | String |
| error | Error | String |

Example

    {
     “errorResponse”: {
          	"errorCode": "403",
          	"errorMessage": "Invalid Credentials",
          	"errorDescription": "Cause: invalid token",
         	"error": "Forbidden"	}
    }
    Copy to clipboard

Note:  All members of the errorResponse structure are optional, thus
        Aware Cloud may not always return all fields.

If you get a 'protocol error cause' in the error field of the error response, submit a case
        to QTI at [https://mysupport.qualcomm.com/aware/s/](https://mysupport.qualcomm.com/aware/s/) with the complete error
        response for further analysis.

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

Last Published: Jul 16, 2025

[Previous Topic
Location service endpoint](https://docs.qualcomm.com/bundle/publicresource/80-63441-4/topics/LaaS-location-service.md) [Next Topic
REST API error codes](https://docs.qualcomm.com/bundle/publicresource/80-63441-4/topics/LaaS-REST-API-error-codes.md)