Documentation/canton-network-docs/Splice APIsScan APIsScan APIView on canton-network-docs ↗
canton-network-docs/Splice APIsScan APIsScan API

POST /v2/updates

POST
/
v2
/
updates
Try it
POST /v2/updates

cURL

curl --request POST \
  --url https://scan.sv-1.global.canton.network.sync.global/api/scan/v2/updates \
  --header 'Content-Type: application/json' \
  --data '
{
  "page_size": 123
}
'
200
400
500
{
  "transactions": [
    {
      "update_id": "<string>",
      "migration_id": 123,
      "workflow_id": "<string>",
      "record_time": "<string>",
      "synchronizer_id": "<string>",
      "effective_at": "<string>",
      "root_event_ids": [
        "<string>"
      ],
      "events_by_id": {},
      "external_transaction_hash": "<string>"
    }
  ]
}

Body

application/json
​
page_size
integer<int32>
required

The maximum number of transactions returned for this request.

​
after
object

The transactions returned will either have a higher migration id or the same migration id and a record_time greater than the migration id and record time specified.

Show child attributes

​
daml_value_encoding
enum<string>

How daml values should be encoded in the response. "compact_json" is a compact, human-readable JSON encoding. It is the same encoding as the one used in the HTTP JSON API or the JavaScript codegen. "protobuf_json" is a verbose JSON encoding that is more difficult to parse, but contains type information, i.e., the values can be parsed losslessly without having access to the Daml source code. Optional and defaults to "compact_json".

Available options:
compact_json,
protobuf_json

Response

200
application/json

ok

​
transactions
object[]
required

An individual item in the update history. May be a transaction or a contract reassignment.

  • Option 1
  • Option 2

Show child attributes