Get transaction by offset
POST
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
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). Requiredstring[]
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 of
3.5.0Changed
3.5The POST /v2/updates/transaction-by-offset operation changed in this snapshot.
Deprecated
3.4Introduced
3.4