API Reference

EXPERIMENTAL_changes-{single_access_key_changes}

Returns the individual access key changes within a specific block. An array of objects containing the account_id and public_key can be used to query multiple keys.

📘

Supported on NEAR (mainnet) only.

Parameters

  • changes_type- string - The type of changes
  • keys- string - An array of maps in the format [{account_id, publick_key}]
  • finality- string - The assurance that the transaction cannot be altered, reversed, or canceled after they are completed. For finality=final, it means that it has been validated on at least 66% of the nodes in the network and for finality=optimistic, it uses the latest block recorded on the node that responded to the query passed
  • block_id- int/string - The block id, it could be either block number or block hash

Note: You can only use one parameter, either finality or block_id. The block_id param can take either the block number or the block hash as an argument.

Returns

  • block_hash - The hash of the block this transaction was associated with
  • changes - An array of changes that occurred in the account during the transaction
    • cause - The reason behind the account changes
      • type - The change causing factor in an account. It could be transaction_processing or receipt_processing
      • tx_hash/receipt_hash - There can be two values returned dependent on the change-causing factor. For transaction_processing, the returned value is tx_hash, which represents the hash of the transaction. For receipt_processing, the returned value is receipt_hash, which represents the hash of the receipt.
    • type - The type of changes occurred in the account
    • change - The changes occurred in the account during the transaction
      • account_id - The identifier for the account
      • public_key - The public key of the signer
      • access_key - The access key for authenticating the account
        • nonce - The number of transactions made by the sender prior to this one encoded as hexadecimal
        • permission - The type of permission

API Endpoint

The format of a Near API endpoint is
https://open-platform.nodereal.io/{{apiKey}}/near/

Here is an example:
https://open-platform.nodereal.io/4c0a1c23661a4e26bcbcwed461e34ea9/near/

Example

Request

curl https://open-platform.nodereal.io/{{apiKey}}/near/ \
--request POST \
--header "Content-Type: application/json" \
--data '{"method": "EXPERIMENTAL_changes","params": {"changes_type": "single_access_key_changes", "keys":[{"account_id": "relay.aurora", "public_key": "ed25519:168vdqFUxij2yvsxYgAGoykJMX7tgrPKVCH484A8nHP"}], "finality": "final"},"id":1,"jsonrpc":"2.0"}'

Result