**Deprecated**, use /v2/updates instead

POST /api/scan/v0/updates

Request

curl --request POST \
  --url 'https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/updates' \
  --header 'Content-Type: application/json' \
  --data '{"after":{"after_migration_id":0,"after_record_time":"string"},"page_size":0,"lossless":false}'

200 response

{
  "transactions": [
    {}
  ]
}

Scan API

Deprecated, use /v2/updates instead

OpenAPISince 0.5.10Changed 0.6.0

Deprecated, use /v2/updates instead. Returns the update history in ascending order, paged, from ledger begin or optionally starting after a record time.

Protocol Details

Operation IDgetUpdateHistory

Published0.7.4

SpecificationDownload OpenAPI

Inputs

Request body

application/json

after · object

OpenAPI type: UpdateHistoryRequestAfter.

page_size · number · required

OpenAPI type: integer (int32).

The maximum number of transactions returned for this request.

lossless · boolean

Whether contract payload should be encoded into json using a lossless, but much harder to process, encoding. This is mostly used for backend calls, and is not recommended for external users. Optional and defaults to false.

Outputs

200

application/json

transactions · UpdateHistoryItem[] · required

400

application/json

error · string · required

500

application/json

error · string · required

History

Changed0.6.0

The POST /v0/updates operation changed in this snapshot.

Changed0.5.17

The POST /v0/updates operation changed in this snapshot.

Deprecated0.5.10

Introduced0.5.10

Request

curl --request POST \
  --url 'https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/updates' \
  --header 'Content-Type: application/json' \
  --data '{"after":{"after_migration_id":0,"after_record_time":"string"},"page_size":0,"lossless":false}'

200 response

{
  "transactions": [
    {}
  ]
}