Skip to main content
POST

JSON Ledger API

Get transaction by offset

OpenAPISince 3.4Changed 3.5Remove as of 3.5.0
Get transaction by offset. Provided for backwards compatibility, it will be removed in the Canton version 3.5.0, use v2/updates/update-by-offset instead.

Protocol Details

Operation IDpostV2UpdatesTransaction-by-offset
AuthenticationBearer token
Published3.5

Inputs

Request body

application/json
number
required
OpenAPI type: integer (int64).The offset of the transaction being looked up. Must be a valid absolute offset (positive integer). Required
string[]
Provided for backwards compatibility, it will be removed in the Canton version 3.5.0. The parties whose events the client expects to see. Events that are not visible for the parties in this collection will not be present in the response. Each element must be a valid PartyIdString (as described in value.proto). Optional for backwards compatibility for GetTransactionByOffset request: if defined transaction_format must be unset (falling back to defaults).
object
OpenAPI type: TransactionFormat.A format that specifies what events to include in Daml transactions and what data to compute and include for them.

Outputs

200

application/json
JsTransaction
required
Filtered view of an on-ledger transaction’s create and archive events.

400

text/plain
string
required

default

application/json
string
required
string
required
string
string
Map_String
required
Tuple2_String_String[]
integer (int32)
required
integer (int32)
string
boolean

History

Remove as of3.5.0
Changed3.5

The POST /v2/updates/transaction-by-offset operation changed in this snapshot.

Deprecated3.4
Introduced3.4