# TPS user beacon API response

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

A successful Terrestrial Positioning Service (TPS) user beacon API request yields an
                HTTP 200 response status with no body in the response.

## Error responses

An improperly formatted API request yields an HTTP 400 response status with a
                response body as follows:

    {
      "error":
      {
        "errors":[
          {
            "domain":"global",
            "reason":"parseError",
            "message":"Parse Error"
          }
        ],
        "code":400,
        "message":"Parse Error"
      }
    }
    Copy to clipboard

Where:
- `domain` provides the classification for the associated error
                        response. Most observed domains are `global`,
                            `geolocation`, `usageLimits`, and
                            `internalServer`.
- `reason` describes the particular error type.
- `message` provides the short description of the error.

Last Published: Jul 03, 2026

[Previous Topic
Sample TPS user beacon API request](https://docs.qualcomm.com/bundle/publicresource/80-42223-1/topics/sample_user_beacon_api_request.md) [Next Topic
References](https://docs.qualcomm.com/bundle/publicresource/80-42223-1/topics/references.md)