> ## Documentation Index
> Fetch the complete documentation index at: https://docs.whitebit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Service

> Ping the WhiteBIT WebSocket server to check connection health and keep the connection alive.

Check API availability with ping/pong and query the current server time. The Service channel supports one-time queries only — no subscription or push events. Use ping to verify connection health and retrieve the server timestamp for clock synchronization.

<Note>Connect to `wss://api.whitebit.com/ws` — see [WebSocket Overview](/websocket/overview) for protocol details and keepalive requirements.</Note>

## Rate limits

## Update frequency

Client-initiated via `server.time` request. The server enforces a **60-second** ping timeout — send a ping within 60 seconds to keep the connection alive.

## Error codes

## Ping

Send a ping every 50 seconds to keep the connection alive. The server closes the connection after 60 seconds of inactivity.

**Request**

**Response**

## Server time

**Request**

**Response**

`result` is the current server time as a Unix timestamp (integer seconds).