RPC API v1

Reference documentation for the public v1 RPC endpoints on Trac Network mainnet.

Use these endpoints to read ledger state and submit transactions.

Network State

Get current TXV

get

Returns the current transaction validity hash (txv) as hex.

Responses
chevron-right
200

TXV returned successfully.

application/json
get
/v1/txv

Get fee

Returns the fee used for transaction submission.

Get current transaction fee

get
Responses
chevron-right
200

Fee returned successfully.

application/json
get
/v1/fee

Get confirmed length

Returns the current confirmed ledger length.

Get confirmed ledger length

get
Responses
chevron-right
200

Confirmed length returned successfully.

application/json
get
/v1/confirmed-length

Get unconfirmed length

Returns the current unconfirmed ledger length.

Get unconfirmed ledger length

get
Responses
chevron-right
200

Unconfirmed length returned successfully.

application/json
get
/v1/unconfirmed-length

Wallet & Account

Get balance

Returns the current balance for an address.

Get wallet balance

get

Returns balance for the specified wallet address.

confirmed query behavior:

  • missing: defaults to confirmed view

  • true: confirmed view

  • false: unconfirmed view

  • any other value: falls back to unconfirmed view

Path parameters
addressstring · min: 1Required

Wallet/account address.

Query parameters
confirmedstringOptional

Balance endpoint behavior:

  • true for confirmed view
  • false for unconfirmed view
  • omitted => confirmed view
  • any other value => treated as unconfirmed view
Default: true
Responses
chevron-right
200

Balance returned successfully.

application/json
get
/v1/balance/{address}

Get account details

Returns account details for an address.

Get account details

get

Returns account details (roles, keys, balances and license).

confirmed must be exactly true or false.

Path parameters
addressstring · min: 1Required

Wallet/account address.

Query parameters
confirmedstring · enumOptional

Must be exactly true or false.

Default: truePossible values:
Responses
chevron-right
200

Account details returned successfully.

application/json
get
/v1/account/{address}

Transactions - Read

List transaction hashes

Returns transaction hashes for a confirmed-length range.

circle-info

The start length must be less than or equal to the end length. The range must fall within the current confirmed length.

Get transaction hashes by confirmed-length range

get

Returns transaction hashes in inclusive range.

Rules:

  • both params must be integers

  • both params must be non-negative

  • end must be greater than or equal to start

  • max difference is 1000

Path parameters
start_confirmed_lengthintegerRequired

Start of confirmed-length range (inclusive).

end_confirmed_lengthintegerRequired

End of confirmed-length range (inclusive).

Responses
chevron-right
200

Hashes returned successfully.

application/json
get
/v1/tx-hashes/{start_confirmed_length}/{end_confirmed_length}

Get transaction by hash

Returns the transaction payload by hash.

circle-info

If the endpoint supports a confirmed query parameter, use it to select the confirmed view. Use the parameter details shown in the operation for default behavior.

Get confirmed transaction details

get

Returns normalized details for confirmed transaction hash.

Current handler behavior:

  • if not found, returns 404 with { "txDetails": null }

  • hash format is not strictly validated at handler layer

Path parameters
transactionHashstring · min: 1Required

Transaction hash.

Responses
chevron-right
200

Transaction details returned successfully.

application/json
get
/v1/tx/{transactionHash}

Get transaction details

Returns the transaction plus decoded and enriched details.

txDetails.tro example (full field set)

Examples for txDetails.tro should include all fields below. This avoids “missing field” ambiguity in client code.

Get transaction details with confirmation metadata

get

Returns transaction details with confirmed_length and fee.

confirmed must be exactly true or false.

Path parameters
transactionHashstringRequired

Transaction hash (64-char hex string).

Pattern: ^[A-Fa-f0-9]{64}$
Query parameters
confirmedstring · enumOptional

Must be exactly true or false.

Default: truePossible values:
Responses
chevron-right
200

Transaction details returned successfully.

application/json
get
/v1/tx/details/{transactionHash}

Transactions - Write

Resolve transaction payloads (bulk)

Fetches multiple transaction payloads in one request.

circle-info

This endpoint enforces request and response size limits. Split requests into smaller batches when you hit limits.

Get transaction payloads in bulk

post

Returns payloads for provided transaction hash list.

Limits:

  • max 1500 hashes per request

  • request body limit: 1_000_000 bytes

  • response body limit: 2_000_000 bytes

Body
hashesstring[] · min: 1 · max: 1500Required
Responses
chevron-right
200

Payloads returned successfully.

application/json
post
/v1/tx-payloads-bulk

Broadcast signed transaction

Broadcasts a signed transaction payload to the network.

circle-exclamation

Broadcast signed transaction

post

Broadcasts a signed transaction payload.

Request requirements:

  • body must be valid JSON

  • body must contain payload

  • payload must be valid Base64 string

Body
payloadstringRequired

Base64-encoded signed transaction.

Responses
chevron-right
200

Transaction accepted and broadcasted.

application/json
post
/v1/broadcast-transaction

Errors & Limits

Confirmed query behavior

Some read endpoints accept a confirmed query parameter. It selects a confirmed view versus an unconfirmed view. Treat it as a consistency knob for reads.

tx-hashes range constraints

Ranges are constrained by confirmed length. Invalid ranges should be treated as client errors. Request smaller windows if you hit server limits.

Bulk request limits

/v1/tx-payloads-bulk is designed for batching. Keep batches small and bounded.

Broadcast rate limiting

/v1/broadcast-transaction can respond with 429. Back off and retry.

Schemas

Last updated