Profile REST Operations for Oracle Radio
Identify the current Radio user and inspect management and Priority Talk capabilities.
The caller must be authenticated, enabled in Radio, and have radio.channel.list. Review permissions if the profile request is denied.
The paths below start at the managed instance origin. When using the returned serviceEndpoint, append only the portion after /api/. See the REST overview for endpoint, authentication, and request guidance.
Get Your Profile
Operation: getRadioProfile.
GET /api/v1/radio/meReturn the Radio-owned profile for the authenticated caller.
No request body or query parameters are required.
Success: 200 with radioUserId and capabilities. The capabilities object contains Boolean manageUsers, manageGroups, and priorityTalk properties. displayName and email can be absent or null.
The features.defaultDistanceUnit value is meters or miles. The browser uses this instance default when the user hasn't selected a personal distance unit in Radio settings. This is a display preference; geofence API values remain in meters.
priorityTalk indicates whether the server authorizes the caller for radio.talk.priority.high. Use this capability rather than a role name to decide whether to offer Priority Talk. A client that receives a missing or false value must not offer that control. This capability doesn't replace normal talk permission or channel access; the server still authorizes each floor request.
Verify that radioUserId is the intended user. The management capabilities don't grant every operation permission or channel access. The profile doesn't expose raw Identity Domain token claims. For 401, renew or correct authentication; for 404 NotAuthorizedOrNotFound, have an administrator check enablement and permission.
Next Steps
Follow the quick start for cURL and PowerShell requests, then discover channels.
For failed requests, see errors, troubleshooting, and the FAQ. A 404 NotAuthorizedOrNotFound response doesn't distinguish missing resources from authorization failures.