Sigil documentation
ReferenceJSON-RPC

sigil_getDidIdentityNft

Fetch the DID-identity index for a subject DID.

Method

sigil_getDidIdentityNft 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.

Fetch the DID-identity index for a subject DID.

Request binding

Source handler: rpc_nft::handle_get_did_identity_nft in sigil/node/sigil-node/src/rpc_nft.rs, line 185.

The handler uses no directly named params.get fields, or delegates input parsing to a typed helper. Use the request types below rather than assuming an empty parameter object.

Parsing excerpt

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

    let subject_did = match extract_string_param(&req.params, 0, "subject_did") {
        Some(s) => s,
        None => {
            return RpcResponse::error(req.id.clone(), -32602, "missing 'subject_did' parameter")
        }
    };

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