Cloud-to-cloud — authorize with an Organization Auth Token.
https://api.location.nrfcloud.com/v1/organizations/{organizationSlug}/projects/{projectSlug}/location/gnss
Device-to-cloud — authorize with a JSON Web Token.
https://api.location.nrfcloud.com/v1/location/gnss
Report device coordinates, commonly obtained from the device's GNSS modem.
__Basic Request__:
```sh
curl --location --request POST "$API_HOST/v1/location/gnss" \
--header "Authorization: Bearer $JWT" \
--header "Content-Type: application/json" \
--data-raw "{\"lat\":$LAT, \"lon\":$LON, \"spd\":$SPD, \"acc\":$ACC, \"alt\":$ALT, \"hdg\":$HDG}"
```
## 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
- GpsRequest
- `lat` number, double, required — WGS 84 geodetic grid line, north to south.
- `lon` number, double, required — WGS 84 geodetic grid line, east to west.
- `acc` number, double — Accuracy in (2D 1-sigma) in meters.
- `alt` number, double — Altitude above WGS 84 ellipsoid in meters.
- `spd` number, double — Horizontal speed in meters per second.
- `hdg` number, double — Heading of movement in degrees.
- string — NMEA 0183 GNSS sentence. See