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
200
Transaction details returned successfully.
application/json
404
Transaction not found.
application/json
500
Internal server error.
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
200
Transaction details returned successfully.
application/json
400
Invalid transaction hash or invalid confirmed parameter.
application/json
404
Transaction not found.
application/json
500
Internal server error.
application/json
get
/v1/tx/details/{transactionHash}
Transactions - Write
Resolve transaction payloads (bulk)
Fetches multiple transaction payloads in one request.
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
200
Payloads returned successfully.
application/json
400
Invalid request body.
application/json
413
Request/response size limits exceeded.
application/json
500
Internal server error.
application/json
post
/v1/tx-payloads-bulk
Broadcast signed transaction
Broadcasts a signed transaction payload to the network.
This endpoint may return 429 Too Many Requests when rate limited. Retry with backoff.
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
200
Transaction accepted and broadcasted.
application/json
400
Invalid request payload.
application/json
429
Broadcast retry limit reached.
application/json
500
Internal server error.
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.