Sigil documentation
ReferenceJSON-RPC

sigil_getAccountTransactions

List recent transactions for a DID.

Method

sigil_getAccountTransactions is registered in the canonical JSON-RPC catalog. Use POST /rpc, Content-Type: application/json, JSON-RPC 2.0 and a caller-controlled request id. Node RPC profile, build feature and runtime activation checks still apply.

List recent transactions for a DID.

Request binding

Source handler: rpc_server::handle_get_account_transactions in sigil/node/sigil-node/src/rpc_server.rs, line 2804.

The handler directly reads these named fields: did, limit, offset, page, page_size. Additional typed parsing, aliases and nested validation are defined by its request types. Field presence alone does not establish optionality.

Parsing excerpt

These source excerpts show binding and validation; they are not runnable client code.

    let did = match req.params.get("did").and_then(|v| v.as_str()) {
        Some(did) => did,
        None => return RpcResponse::error(req.id.clone(), -32602, "missing 'did' parameter"),
    };

        .or_else(|| req.params.get("page_size"))
        .and_then(|v| v.as_u64())
        .unwrap_or(100)
        .clamp(1, 500) as usize;

Responses and failures

Check HTTP status, parse the JSON-RPC envelope, reject error, and require result on success. Preserve large base-unit integers without floating-point rounding. A catalog method does not bypass authentication, capability, policy or activation requirements.

On this page