sigil_getNftToken
Fetch a single NFT token within a collection.
Method
sigil_getNftToken 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 a single NFT token within a collection.
Request binding
Source handler: rpc_nft::handle_get_nft_token in sigil/node/sigil-node/src/rpc_nft.rs, line 74.
The handler directly reads these named fields: token_id. 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 id_str = match extract_string_param(&req.params, 0, "collection_id") {
Some(s) => s,
None => {
return RpcResponse::error(req.id.clone(), -32602, "missing 'collection_id' parameter")
}
};
.or_else(|| req.params.get(1))
.and_then(|v| v.as_str())
{
Some(s) => s.to_string(),
None => return RpcResponse::error(req.id.clone(), -32602, "missing 'token_id' 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.