Location Update REST Operations for Oracle Radio
Report the authenticated user's position and inspect geofence action results.
Location reporting requires radio.location.update. Use the supported authentication flow and follow your organization's location-sharing requirements. The operation records the authenticated user's position; it doesn't update another user by accepting a user ID.
Update Your Location
updateLocation: POST /api/v1/radio/me/location
The path starts at the instance origin. Send Content-Type: application/json and the following properties:
| Property | Requirement |
|---|---|
latitude / longitude | Required numbers: latitude from -90 through 90 and longitude from -180 through 180. |
deviceId | Optional string identifying the reporting device; it does not replace user authentication. |
altitude, speed, heading, course, horizontalAccuracy, verticalAccuracy, speedAccuracy, courseAccuracy, batteryLevel | Optional numbers. Omit telemetry you do not have; use the reporting client's supported values. |
floor | Optional integer. |
batteryState / networkType | Optional strings. |
timestamp / recordedAt | Optional date-time strings with timezone information. |
A minimal request contains the reported coordinates. These coordinates are illustrative; replace them with the location you intend to report.
{"latitude":38.9,"longitude":-77.04}HTTP 200 returns location with latitude and longitude, and an actions array. An empty array means no geofence action was returned for this update.
Each action includes action, channel, userId, distance, and status. Check each status:
| Status | Meaning |
|---|---|
APPLIED | The saved-subscription action was applied. |
NOT_AUTHORIZED_OR_NOT_FOUND | The action could not be authorized or its resource was unavailable. The response does not identify which check failed. |
FAILED | The action failed. Inspect saved state and the operation's error guidance before retrying. |
A successful location response doesn't guarantee that every membership action succeeded, that the position is retained in location history, or that the current WebSocket connection joined a channel. Verify saved subscriptions and live membership separately. Applied changes can produce membership notifications.
For browser reporting, use location sharing. For failed actions, see geofence troubleshooting.