Export ledger entries

Export ledger entries records ledger entries to a csv file. May or may not contain a date range - if no date range is provided, list all records for all times.

Ledger entries can be exported by:

• export ledger entries for a single party for a given asset within a given time range
• export ledger entries for a single party for a given asset for all times buf:lint:ignore RPC_RESPONSE_STANDARD_NAME buf:lint:ignore RPC_REQUEST_RESPONSE_UNIQUE

Query Parameters

partyId string required

Party ID to export ledger entries for.

assetId string required

Optional: Asset ID.

dateRange.startTimestamp int64
dateRange.endTimestamp int64

Responses

• 200
• 500
• default

---

A successful response.(streaming responses)

application/json

Schema

Example (from schema)

---

Schema

error object
code int32
details object[]
@type string
message string
result object
Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page.
This message can be used both in streaming and non-streaming API methods in the request as well as the response.
It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body.
Example:
message GetResourceRequest {
  // A unique request id.
  string request_id = 1;

  // The raw HTTP body is bound to this field.
  google.api.HttpBody http_body = 2;

}

service ResourceService {
  rpc GetResource(GetResourceRequest)
    returns (google.api.HttpBody);
  rpc UpdateResource(google.api.HttpBody)
    returns (google.protobuf.Empty);

}
Example with streaming methods:
service CaldavService {
  rpc GetCalendar(stream google.api.HttpBody)
    returns (stream google.api.HttpBody);
  rpc UpdateCalendar(stream google.api.HttpBody)
    returns (stream google.api.HttpBody);

}
Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged.
contentType string
data byte
extensions object[]
Application specific response metadata. Must be set in the first response for streaming APIs.
@type string

{
  "error": {
    "code": 0,
    "details": [
      {
        "@type": "string"
      }
    ],
    "message": "string"
  },
  "result": {
    "contentType": "string",
    "data": "string",
    "extensions": [
      {
        "@type": "string"
      }
    ]
  }
}

An internal server error

application/json

Schema

Example (from schema)

---

Schema

code int32
details object[]
@type string
message string

{
  "code": 0,
  "details": [
    {
      "@type": "string"
    }
  ],
  "message": "string"
}

An unexpected error response.

application/json

Schema

Example (from schema)

---

Schema

code int32
details object[]
@type string
message string

{
  "code": 0,
  "details": [
    {
      "@type": "string"
    }
  ],
  "message": "string"
}

GET /api/v2/ledgerentry/export

Request

Base URL

https://api.n06.testnet.vega.xyz

partyId — query required

assetId — query required

dateRange.startTimestamp — query

dateRange.endTimestamp — query

curl / cURL

curl -L -X GET 'https://api.n06.testnet.vega.xyz/api/v2/ledgerentry/export' \
-H 'Accept: application/json'

python / requests

curl -L -X GET 'https://api.n06.testnet.vega.xyz/api/v2/ledgerentry/export' \
-H 'Accept: application/json'

go / native

curl -L -X GET 'https://api.n06.testnet.vega.xyz/api/v2/ledgerentry/export' \
-H 'Accept: application/json'

nodejs / axios

curl -L -X GET 'https://api.n06.testnet.vega.xyz/api/v2/ledgerentry/export' \
-H 'Accept: application/json'