Files
xrpl-dev-portal/docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md
mDuo13 7645140477 Re-levelization: move non-docs content, rename content→docs
For better URLs, the content folder has been renamed 'docs' and all
other files have been moved up a level. Also, non-docs images have been
moved to the static folder at the top level where they belong.

Many relative paths had to be fixed to make this work.
2024-01-31 17:53:52 -08:00

90 lines
1.4 KiB
Markdown

---
html: ping.html
parent: utility-methods.html
seo:
description: Confirm connectivity with the server.
labels:
- Core Server
---
# ping
[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Ping.cpp "Source")
The `ping` command returns an acknowledgement, so that clients can test the connection status and latency.
## Request Format
An example of the request format:
{% tabs %}
{% tab label="WebSocket" %}
```json
{
"id": 1,
"command": "ping"
}
```
{% /tab %}
{% tab label="JSON-RPC" %}
```json
{
"method": "ping",
"params": [
{}
]
}
```
{% /tab %}
{% tab label="Commandline" %}
```sh
#Syntax: ping
rippled ping
```
{% /tab %}
{% /tabs %}
[Try it! >](/resources/dev-tools/websocket-api-tool#ping)
The request includes no parameters.
## Response Format
An example of a successful response:
{% tabs %}
{% tab label="WebSocket" %}
```json
{
"id": 1,
"result": {},
"status": "success",
"type": "response"
}
```
{% /tab %}
{% tab label="JSON-RPC" %}
```json
200 OK
{
"result": {
"status": "success"
}
}
```
{% /tab %}
{% /tabs %}
The response follows the [standard format][], with a successful result containing no fields. The client can measure the round-trip time from request to response as latency.
## Possible Errors
* Any of the [universal error types][].
{% raw-partial file="/docs/_snippets/common-links.md" /%}