Diagnostic REST Operations for Oracle Radio
Check public Radio connectivity with the health and ping endpoints.
These two GET operations are public and require no authentication or Radio permission. Use the instance's returned serviceEndpoint, which already ends with /api/; append v1/health or v1/ping. Don't add a second /api/ prefix.
A successful diagnostic response doesn't verify sign-in, Radio authorization, or the availability of every Radio operation. There is no public readiness endpoint.
Check Health
health: GET /api/v1/health
No body or query parameters are required. HTTP 200 returns JSON with status, version, uptime in seconds, and timestamp, plus connections, auth, rateLimiting, and permissions summaries.
This is an application health response, not a dependency-readiness test. Don't use its version value to select a client contract or identify the Radio UI version.
Check Connectivity
ping: GET /api/v1/ping
No body or query parameters are required. HTTP 200 returns pong set to true and a timestamp. This HTTP operation is separate from the WebSocket PING message.
For a failed check, verify the returned endpoint and path, then follow diagnostic troubleshooting.