getTime — TON JSON-RPC

Status: Available

Returns the current Unix time reported by the selected TON liteserver.

TON RPC node endpoint · Best TON RPC providers compared

POSThttps://triport.io/rpc/ton

Network: TON mainnet
Scope: ton:rpc
Auth: x-token: $TRIPORT_API_KEY
Rate limit: free+; ton_read_rpc: 15 / 20 / 100 / 250 RPS sustained · short burst 30 / 40 / 200 / 500 (free / basic / pro / business; default, unmeasured); Burst capacity

Request

cURLJavaScriptPython

curl https://triport.io/rpc/ton \
  -H "x-token: $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"getTime","params":{}}'

const res = await fetch("https://triport.io/rpc/ton", {
  method: "POST",
  headers: {
    "x-token": process.env.TRIPORT_API_KEY,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getTime",
    "params": {}
  }),
});
const data = await res.json();
console.log(data);

import os


import requests


resp = requests.post(
    "https://triport.io/rpc/ton",
    headers={
        "x-token": os.environ["TRIPORT_API_KEY"],
        "Content-Type": "application/json",
    },
    json={
        "jsonrpc": "2.0",
        "id": 1,
        "method": "getTime",
        "params": {},
    },
)
data = resp.json()
print(data)

Response

JSON

Example

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "now": 1788347578
  }
}

Liteserver call over ADNL: liteServer.getTime. See lite_api.tl (checked 2026-10-25).

getTime returns the current time reported by the selected liteserver. The result is a Unix timestamp in the now field and represents that server's clock at the time of the response.

Use it for liteserver diagnostics or coarse clock comparison. It is not a TON block position and must not replace masterchain seqno or transaction logical time (lt) when ordering chain data.

This direct liteserver method has no separate HTTP-gateway compatibility promise. The Triport JSON-RPC facade calls the ADNL liteserver pool.

Parameters

JSON-RPC params is an empty by-name object.

Params: object (by-name).

——optional

This method has no parameters; send params: {}.

Response

Response fields

Field	Type	Description
`jsonrpc`	string	JSON-RPC protocol version.
`id`	number or string	Correlates the response with the request.
`result`	object	Liteserver time result.
`result.now`	integer	Unix timestamp reported by the selected liteserver.

The response is copied from the accepted live fixture.

Errors

See TON errors for the shared envelope.

Code	Meaning	When it happens
`-32602`	Invalid params	The parameter structure is malformed or positional.
`-32601`	Method not found	The method is outside the published read-only catalog.
`401`	Unauthorized	The API key is missing or invalid.
`429`	Rate limited	The `ton_read_rpc` budget is exceeded.

Examples

JavaScript

const response = await fetch("https://triport.io/rpc/ton", {
  method: "POST",
  headers: { "x-token": process.env.TRIPORT_API_KEY, "Content-Type": "application/json" },
  body: JSON.stringify({ jsonrpc: "2.0", id: "clock", method: "getTime", params: {} }),
});
const { result: serverTime } = await response.json();

Notes

now is diagnostic server time, not consensus time, block seqno, or transaction lt.
Calls use named params. When batched, correlate results by JSON-RPC id.
Poll this method if needed; TON WebSocket subscriptions are not published. Public HTTP gateways are not used as upstreams.
Related methods: getVersion and getMasterchainInfo.
TON RPC endpoint and plans.