Checking an Oracle Radio WebSocket Connection
Send a PING message to confirm that an established Radio WebSocket connection can exchange messages.
Permissions and Prerequisites
The following permissions and prerequisites apply to this operation.
| Requirement | Value |
|---|---|
| Authentication | Authentication is optional for PING. A PONG response confirms message exchange but doesn't mean that a bearer-token client completed AUTH. See authentication. |
| Radio permission | No operation-specific Radio permission is required. |
| Channel access | No channel access or channel subscription is required. |
| Session state | The WebSocket connection must be open. |
Request
Send the PING message as a JSON text message.
| Name | Data type | Required | Default | Constraints | Description |
|---|---|---|---|---|---|
type | string | Yes | None | Must be PING. | Identifies the connection-check operation. |
{
"type": "PING"
}Responses
The following table lists the messages the client can receive and explains their purpose.
| Message type | Kind | Description |
|---|---|---|
PONG | Direct response | Confirms that the connection can exchange application messages. |
ERROR | Error | Indicates that the request could not be processed, such as when the JSON message is invalid. |
PONG Response
The following table describes the response properties, their data types, and whether they are required.
| Name | Data type | Required | Description |
|---|---|---|---|
type | string | Yes | Response type. The value is PONG. |
timestamp | string | No | Server date and time in ISO 8601 format. |
{
"type": "PONG",
"timestamp": "2026-09-02T14:30:00Z"
}