Cloud-to-cloud — authorize with an Organization Auth Token.
https://api.location.nrfcloud.com/v1/organizations/{organizationSlug}/projects/{projectSlug}/location/ground-fix
Device-to-cloud — authorize with a JSON Web Token.
https://api.location.nrfcloud.com/v1/location/ground-fix
Gets the lat, lon, and uncertainty values for the LTE/GSM/WCDMA cell(s) or wifi access points passed. Wifi will be prioritized and fall back to cell if unavailable. At least one cell or two Wi-Fi access points are required. An empty `lte`, `ltecatm`, `nbiot`, `gsm`, `wcdma`, or `wifi` array is treated the same as an omitted field.
Return JSON payload.
__Basic Request__:
```sh
curl -X POST "$API_HOST/v1/location/ground-fix" -H "Authorization: Bearer $JWT" -H "Content-Type: application/json" -d "{\"lte\":[{\"mcc\": 244, \"mnc\": 91,\"tac\": 4099,\"eci\":36078631}], \"wifi\":[{\"macAddress\": \"00-18-39-59-8C-53\", \"ssid\": \"my-wifi-network\", \"signalStrength\": -42}, {\"macAddress\": \"00:21:55:61:F3:0A\", \"ssid\": \"my-other-wifi-network\", \"signalStrength\": -22}]}"
```
__Save device location and silence response__:
```sh
curl --verbose -X POST "$API_HOST/v1/location/ground-fix?doReply=false" -H "Authorization: Bearer $JWT" -H "Content-Type: application/json" -d "{\"lte\":[{\"mcc\": 244, \"mnc\": 91,\"tac\": 4099,\"eci\":36078631}], \"wifi\":[{\"macAddress\": \"00-18-39-59-8C-53\", \"ssid\": \"my-wifi-network\", \"signalStrength\": -42}, {\"macAddress\": \"00:21:55:61:F3:0A\", \"ssid\": \"my-other-wifi-network\", \"signalStrength\": -22}]}"
```
## Query parameters
- `doReply` union — Controls the response body. If boolean false or number 0, response body will be empty.
- boolean
- number, double
- `fallback` boolean — nRF Cloud will always return the most accurate response based on cell tower location or AP location for wifi, if available. When not available, nRF Cloud falls back to area-level location estimate based on cell tower tracking area code. To disable this behavior, set fallback=false. This will ignore cell tracking area and return a 404 in event a higher accuracy response cannot be provided.
- `hiConf` boolean — nRF Cloud automatically uses a 68% confidence interval when estimating the Horizontal Positioning Error (HPE) for a location. This means that there is a 68% probability that the device's actual location is within the HPE radius of the returned coordinates. Enabling this flag will use a 95% confidence interval instead, resulting in a larger HPE radius, and a higher probability that the device's actual location is within the circle.
- `dist` number, double — nRF Cloud combats stale and inaccurate Wi-Fi location data by comparing the distance between Wi-Fi and cell location (if provided). This parameter allows the user to customize this behavior by setting the distance threshold used in that comparison, with the requirement that cell location is also provided in the request. Measured in meters (m).
- `alt` boolean — nRF Cloud makes its best effort to return the most quality location data possible. Sometimes that means choosing one location and throwing out the other. These details are omitted from the response to keep a small and succinct payload. Sending alt=true will allow you to see this alternate location and its distance from the chosen location in meters.
- `reverseGeo` boolean — When enabled, the response will include reverse-geocoded address data for the resolved coordinates. This adds a `reverseGeo` property to the response containing the address, formatted address string, and the coordinates/uncertainty of the resolved address. Note: enabling this flag results in two API requests internally — one for the geolocation and one for the reverse geocoding lookup, which each get charged independently.
## Headers
- `x-custom-device-id` string — User-defined device ID, used to identify requests when using a cloud-to-cloud integration. Ignored if using a device token.
## Request body
- union
- GroundFixRequest
- `lte` LteCell[]
- `rsrp` number, double — Reference Signal Received Power. Measured in dBm. See