Skip to main content
POST
/
95e61622bf6a8af293978377718e3b77
/
wallet
/
getincomingviewingkey
wallet/getincomingviewingkey
curl --request POST \
  --url https://tron-mainnet.core.chainstack.com/95e61622bf6a8af293978377718e3b77/wallet/getincomingviewingkey \
  --header 'Content-Type: application/json' \
  --data '
{
  "ak": "03b2c3d4e5f67890123456789012345678901234567890123456789012345678",
  "nk": "04c3d4e5f6789012345678901234567890123456789012345678901234567890"
}
'
{
  "ivk": "05d4e5f6789012345678901234567890123456789012345678901234567890abcdef"
}

Documentation Index

Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt

Use this file to discover all available pages before exploring further.

TRON API method that derives an incoming viewing key (ivk) from authentication key (ak) and nullifier key (nk) for shielded TRC20 transactions. The incoming viewing key is used to scan for incoming shielded payments.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • ak — authentication key as a 32‑byte (64‑hex) string, no 0x prefix.
  • nk — nullifier key as a 32‑byte (64‑hex) string, no 0x prefix.

​
Response

  • ivk — the derived incoming viewing key in hexadecimal format

​
Use case

The wallet/getincomingviewingkey method is used for:
  • Generating keys needed to scan for incoming shielded payments
  • Creating viewing keys that allow monitoring received transactions without spending authority
  • Supporting wallet implementations that need to detect incoming shielded transfers
  • Enabling privacy-preserving transaction monitoring

​
curl example

Shell
curl --request POST \
  --url 'https://tron-mainnet.core.chainstack.com/95e61622bf6a8af293978377718e3b77/wallet/getincomingviewingkey' \
  --header 'Content-Type: application/json' \
  --data '{
    "ak": "03b2c3d4e5f67890123456789012345678901234567890123456789012345678",
    "nk": "04c3d4e5f6789012345678901234567890123456789012345678901234567890"
  }'
All keys must be exactly 64 hexadecimal characters without a 0x prefix. Otherwise the node returns an error like: “param length must be 32”.

Body

application/json
​
ak
string
required

Authentication key (ak) as a 32‑byte (64‑hex) string without 0x prefix.

Pattern: ^[0-9a-fA-F]{64}$
Example:

"03b2c3d4e5f67890123456789012345678901234567890123456789012345678"

​
nk
string
required

Nullifier key (nk) as a 32‑byte (64‑hex) string without 0x prefix.

Pattern: ^[0-9a-fA-F]{64}$
Example:

"04c3d4e5f6789012345678901234567890123456789012345678901234567890"

Response

200 - application/json

Successfully derived incoming viewing key

​
ivk
string

The derived incoming viewing key (ivk) in hexadecimal format (no 0x prefix)

Example:

"05d4e5f6789012345678901234567890123456789012345678901234567890abcdef"

Last modified on April 29, 2026