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

OpenAPI Updated 0.6.0 Deprecated 0.5.10 Added 0.5.10

```bash cURL theme={null} 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": 123, "after_record_time": "" }, "page_size": 123, "lossless": false }' ``` ```python Python theme={null} import json import requests url = "https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/updates" headers = {'Content-Type': 'application/json'} payload = json.loads(r'''{ "after": { "after_migration_id": 123, "after_record_time": "" }, "page_size": 123, "lossless": false }''') response = requests.request( "POST", url, headers=headers, json=payload ) print(response.text) ``` ```javascript JavaScript theme={null} const response = await fetch('https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/updates', { method: 'POST', headers: { "Content-Type": "application/json" }, body: JSON.stringify({ "after": { "after_migration_id": 123, "after_record_time": "" }, "page_size": 123, "lossless": false }), }); console.log(await response.text()); ``` ```php PHP theme={null} 'https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/updates', CURLOPT_RETURNTRANSFER => true, CURLOPT_CUSTOMREQUEST => 'POST', CURLOPT_POSTFIELDS => <<<'JSON' { "after": { "after_migration_id": 123, "after_record_time": "" }, "page_size": 123, "lossless": false } JSON, CURLOPT_HTTPHEADER => [ "Content-Type: application/json" ], ]); $response = curl_exec($curl); echo $response; ``` ```go Go theme={null} package main import ( "bytes" "fmt" "io" "net/http" ) func main() { req, _ := http.NewRequest("POST", "https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/updates", bytes.NewBufferString(`{ "after": { "after_migration_id": 123, "after_record_time": "" }, "page_size": 123, "lossless": false }`)) req.Header.Set("Content-Type", "application/json") response, _ := http.DefaultClient.Do(req) defer response.Body.Close() body, _ := io.ReadAll(response.Body) fmt.Println(string(body)) } ``` ```java Java theme={null} import java.net.URI; import java.net.http.HttpClient; import java.net.http.HttpRequest; import java.net.http.HttpResponse; var request = HttpRequest.newBuilder() .uri(URI.create("https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/updates")) .header("Content-Type", "application/json") .method("POST", HttpRequest.BodyPublishers.ofString(""" { "after": { "after_migration_id": 123, "after_record_time": "" }, "page_size": 123, "lossless": false } """)) .build(); var response = HttpClient.newHttpClient().send( request, HttpResponse.BodyHandlers.ofString()); System.out.println(response.body()); ``` ```ruby Ruby theme={null} require 'net/http' require 'uri' uri = URI('https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/updates') request = Net::HTTP::Post.new(uri) request['Content-Type'] = 'application/json' request.body = <<~JSON { "after": { "after_migration_id": 123, "after_record_time": "" }, "page_size": 123, "lossless": false } JSON response = Net::HTTP.start(uri.hostname, uri.port) do |http| http.request(request) end puts response.body ``` ```json 200 theme={null} { "transactions": [ { "update_id": "", "migration_id": 123, "workflow_id": "", "record_time": "", "synchronizer_id": "", "effective_at": "", "offset": "", "root_event_ids": [ "" ], "events_by_id": {}, "external_transaction_hash": "" } ] } ``` ```json 400 theme={null} { "error": "" } ``` ```json 500 theme={null} { "error": "" } ``` ## Body

application/json

OpenAPI type: UpdateHistoryRequestAfter. 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. OpenAPI type: integer (int64). The migration id from which to start returning transactions. This is inclusive. The record time to start returning transactions from. This only affects transactions with the same migration id as after\_migration\_id. Higher migration ids are always considered to be later. OpenAPI type: integer (int32). The maximum number of transactions returned for this request. 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. ## Responses ### 200 ok

application/json

The id of the update. The migration id of the synchronizer. This transaction's Daml workflow ID; a workflow ID can be associated with multiple transactions. If empty, no workflow ID was set. The time at which the transaction was sequenced, with microsecond resolution, using ISO-8601 representation. The id of the synchronizer through which this transaction was sequenced. Ledger effective time, using ISO-8601 representation. This is the time returned by `getTime` for all Daml executed as part of this transaction, both by the submitting participant and all confirming participants. The absolute offset. Note that this field may not be the same across nodes, and therefore should not be compared between SVs. However, within a single SV's scan, it is monotonically, lexicographically increasing. Roots of the transaction tree. These are guaranteed to occur as keys of the `events_by_id` object. Changes to the ledger that were caused by this transaction, keyed by ID. Values are nodes of the transaction tree. Within a transaction, IDs may be referenced by `root_event_ids` or `child_event_ids` in `ExercisedEvent` herein. For an externally signed transaction, contains the external transaction hash signed by the external party. Can be used to correlate an external submission with a committed transaction. This field is conditionally omitted from JSON when null (see OmitNullString). A contract reassignment between synchronizer. May be an assignment or unassignment. The id of the update. The absolute offset. Note that this field may not be the same across nodes, and therefore should not be compared between SVs. The time at which the transaction was sequenced. The reassignment event. May be an assignment or unassignment. The party ID who submitted this reassignment The id of the synchronizer from which the contract was reassigned The id of the synchronizer to which the contract was reassigned The migration id of the target synchronizer The id of the corresponding unassign event; this assignment will usually, but not always, occur after the so-identified unassignment event. The corresponding contract create event The ID of this particular event. Equal to the key of this element of the containing `events_by_id` if this is part of a `TreeEvent`. The ID of the created contract. The template of the created contract. The package name of the created contract. The arguments that have been used to create the contract, in the form of JSON representation of a Daml record. Ledger effective time of the transaction that created the contract. Signatories to the contract, in the form of party IDs. Observers to the contract, in the form of party IDs. Each corresponding assigned and unassigned event has the same reassignment\_counter. This strictly increases with each unassign command for the same contract. Creation of the contract corresponds to reassignment\_counter 0. The party who submitted this reassignment The id of the synchronizer from which the contract was reassigned The migration id of the synchronizer from which the contract was reassigned The id of the synchronizer to which the contract was reassigned The id of the unassign event, to later be correlated to an assign event Each corresponding assigned and unassigned event has the same reassignment\_counter. This strictly increases with each unassign command for the same contract. Creation of the contract corresponds to reassignment\_counter 0. The id of the unassigned contract ### 400 bad request

application/json

### 500 internal server error

application/json

## History

Updated 0.6.0

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

Updated 0.5.17

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

Deprecated 0.5.10

Added 0.5.10