Returns the event with the given update\_id. An event bears some combination of a transaction, a contract reassignment, and a verdict.

OpenAPI Present since at least 0.5.10 Updated 0.6.10

```bash cURL theme={"theme":{"light":"github-light","dark":"github-dark"}} curl --request GET \ --url 'https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/events/{update_id}' ``` ```python Python theme={"theme":{"light":"github-light","dark":"github-dark"}} import json import requests url = "https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/events/{update_id}" response = requests.request("GET", url) print(response.text) ``` ```javascript JavaScript theme={"theme":{"light":"github-light","dark":"github-dark"}} const response = await fetch('https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/events/{update_id}', { method: 'GET', }); console.log(await response.text()); ``` ```php PHP theme={"theme":{"light":"github-light","dark":"github-dark"}} 'https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/events/{update_id}', CURLOPT_RETURNTRANSFER => true, CURLOPT_CUSTOMREQUEST => 'GET', ]); $response = curl_exec($curl); echo $response; ``` ```go Go theme={"theme":{"light":"github-light","dark":"github-dark"}} package main import ( "fmt" "io" "net/http" ) func main() { req, _ := http.NewRequest("GET", "https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/events/{update_id}", nil) response, _ := http.DefaultClient.Do(req) defer response.Body.Close() body, _ := io.ReadAll(response.Body) fmt.Println(string(body)) } ``` ```java Java theme={"theme":{"light":"github-light","dark":"github-dark"}} 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/events/{update_id}")) .method("GET", HttpRequest.BodyPublishers.noBody()) .build(); var response = HttpClient.newHttpClient().send( request, HttpResponse.BodyHandlers.ofString()); System.out.println(response.body()); ``` ```ruby Ruby theme={"theme":{"light":"github-light","dark":"github-dark"}} require 'net/http' require 'uri' uri = URI('https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/events/{update_id}') request = Net::HTTP::Get.new(uri) response = Net::HTTP.start(uri.hostname, uri.port) do |http| http.request(request) end puts response.body ``` ```json 200 theme={"theme":{"light":"github-light","dark":"github-dark"}} { "update": { "update_id": "", "migration_id": 123, "workflow_id": "", "record_time": "", "synchronizer_id": "", "effective_at": "", "root_event_ids": [ "" ], "events_by_id": {}, "external_transaction_hash": "" }, "verdict": { "update_id": "", "migration_id": 123, "domain_id": "", "record_time": "", "finalization_time": "", "submitting_parties": [ "" ], "submitting_participant_uid": "", "verdict_result": "VERDICT_RESULT_UNSPECIFIED", "mediator_group": 123, "transaction_views": { "views": [ { "view_id": 123, "informees": [ "" ], "confirming_parties": [ { "parties": [ "" ], "threshold": 123 } ], "sub_views": [ 123 ], "view_hash": "" } ], "root_views": [ 123 ] } }, "traffic_summary": { "total_traffic_cost": 123, "envelope_traffic_summaries": [ { "traffic_cost": 123, "view_ids": [ 123 ] } ] }, "app_activity_records": { "round_number": 123, "records": [ { "party": "", "weight": 123 } ] } } ``` ```json 400 theme={"theme":{"light":"github-light","dark":"github-dark"}} { "error": "" } ``` ```json 404 theme={"theme":{"light":"github-light","dark":"github-dark"}} { "error": "" } ``` ```json 500 theme={"theme":{"light":"github-light","dark":"github-dark"}} { "error": "" } ``` ## Path parameters ## Query parameters OpenAPI type: DamlValueEncoding. 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". Allowed values: compact\_json, protobuf\_json. ## Responses ### 200 ok

application/json

An individual item in the update history. May be a transaction or a contract reassignment. 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. 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 and sorted lexicographically by ID for display consistency. 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, which are sorted in the order as they occurred in the transaction. 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 The ID of the transaction update associated with this verdict. The migration id of the domain through which this event was sequenced. The id of the domain through which this event was sequenced. The record\_time of the transaction the verdict corresponds to. The finalization\_time of the transaction the verdict corresponds to. Note that this time might be different between different scans/mediators. Parties on whose behalf the transaction was submitted. UID of the submitting participant. Result of the verdict. Allowed values: VERDICT\_RESULT\_UNSPECIFIED, VERDICT\_RESULT\_ACCEPTED, VERDICT\_RESULT\_REJECTED. The mediator group which finalized this verdict. Hash of the view, for correlation with sequencer traffic data. Empty for older data ingested before this field was added. Traffic summary data from the sequencer for the confirmation request corresponding to an event. Total traffic cost of the confirmation request paid by the validator node that submitted it. Summary of traffic-related data for all envelopes in the confirmation request. Traffic cost in bytes for this envelope. View IDs from the verdict contained in this envelope App activity record computed from verdicts and traffic summaries as per [CIP-104](https://github.com/canton-foundation/cips/blob/main/cip-0104/cip-0104.md). The round number assigned to the activity records. App activity records, one per app provider. The app provider party identifier. Activity weight in bytes of traffic. ### 400 bad request

application/json

### 404 not found

application/json

### 500 internal server error

application/json

## History

Updated 0.6.10

The GET /v0/events/\{update\_id} operation changed in this snapshot.

Updated 0.6.0

The GET /v0/events/\{update\_id} operation changed in this snapshot.

Updated 0.5.17

The GET /v0/events/\{update\_id} operation changed in this snapshot.

Updated 0.5.15

The GET /v0/events/\{update\_id} operation changed in this snapshot.

Present since at least 0.5.10