Supported Operators
Supported Filters
balance
and ticker
JSON keys.Recursive Filtering
.
operator.Supported Verbs
get
- Get object of supported type.
list
- List all objects owned by given user.
history
- Generate the history of all last states.
transactions
- List all transactions that modified specified object.Supported Nouns
account
] - An object register containing a token-id and balance.
[trust
] - An object register containing a token-id, balance, and trust.
[token
] - An object register containing a token-id, balance, supply, and decimals.
[name
] - An object register containing Names and Global Names.
[namespace
] - An object register containing namespaces.
[crypto
] - An object register which holds public key hashes.
[object
] - An object register containing user-defined data structure.
[raw
] - An object register containing raw data.
[readonly
] - An object register which is readonly.
[append
] - An object register which can be appended.
[any
] - An object selection noun allowing mixed accounts of different tokens.
Sorting / Filtering
limit
: The number of records to return. page
: Zero-indexed page number that depends on limit
for page boundaries.offset
: Alternative to page
, offset can be used to page the results by index.order
: Descending desc or ascending asc are only permitted values.sort
: The column or field-name to apply the sorting logic to. This parameter supports moving up levels of JSON keys by using .
, such as sort=json.date
would apply a sort to a nested JSON object:where
: Apply a boolean statement to the results of command, following the SQL-DSL syntax.limit
and offset
parameters can be given with the following format:limit=100
and offset=10
.list
list/account
list/trust
list/token
list/name
list/namespace
list/crypto
list/object
list/readonly
list/raw
list/append
get
account
, trust
and token
nouns.get/account
get/trust
trust
account.get/token
get/name
get/namespace
get/crypto
get/object
get/readonly
get/raw
get/append
session
: When using multi-user API mode the session parameter must be supplied to identify which profile to update.name
: The name identifying the account/trust/token. This is optional if the address is provided.address
: The register address of the account/trust//token to be transferred. This is optional if the name is provided.history
account, trust and token
nouns.history/name
history/namespace
history/crypto
history/object
history/readonly
history/raw
history/append
session
: When using multi-user API mode the session parameter must be supplied to identify which profile to update.name
: The name identifying the account/trust/token. This is optional if the address is provided.address
: The register address of the account/trust//token to be transferred. This is optional if the name is provided.transactions
account, trust and token
nouns.transactions/account
transactions/trust
transactions/token
transactions/name
transactions/namespace
transactions/crypto
transactions/object
transactions/readonly
transactions/raw
transactions/append
session
: Required by argument -multiuser=1
to be supplied to identify the user session that is creating the transaction.verbose
: Optional, determines how much transaction data to include in the response. Supported values are :default
: hashsummary
: type, version, sequence, timestamp, operation, and confirmations.detail
: genesis, nexthash, prevhash, pubkey and signature.txid
: The transaction hash.type
: The description of the transaction (legacy
| tritium base
| trust
| genesis
| user
).version
: The serialization version of the transaction.sequence
: The sequence number of this transaction within the signature chain.timestamp
: The Unix timestamp of when the transaction was created.blockhash
: The hash of the block that this transaction is included in. Blank if not yet included in a block.confirmations
: The number of confirmations that this transaction obtained by the network.genesis
: The signature chain genesis hash.nexthash
: The hash of the next transaction in the sequence.prevhash
: the hash of the previous transaction in the sequence.pubkey
: The public key.signature
: The signature hash.contracts
: The array of contracts bound to this transaction and their details with opcodes.
{
id
: The sequential ID of this contract within the transaction.OP
: The contract operation. Can be APPEND
, CLAIM
, COINBASE
, CREATE
, CREDIT
, DEBIT
, FEE
, GENESIS
, LEGACY
, TRANSFER
, TRUST
, STAKE
, UNSTAKE
, WRITE
.for
: For CREDIT
transactions, the contract that this credit was created for . Can be COINBASE
, DEBIT
, orLEGACY
.txid
: The transaction that was credited / claimed.contract
: The ID of the contract within the transaction that was credited / claimed.proof
: The register address proving the credit.from
: For DEBIT
, CREDIT
, FEE
transactions, the register address of the account that the debit is being made from.from_name
: For DEBIT
, CREDIT
, FEE
transactions, the name of the account that the debit is being made from. Only included if the name can be resolved.to
: For DEBIT
and CREDIT
transactions, the register address of the recipient account.to_name
: For DEBIT
and CREDIT
transactions, the name of the recipient account. Only included if the name can be resolved.amount
: the token amount of the transaction.token
: the register address of the token that the transaction relates to. Set to 0 for NXS transactionstoken_name
: The name of the token that the transaction relates to.reference
: For DEBIT
and CREDIT
transactions this is the user supplied reference used by the recipient to relate the transaction to an order or invoice number.object
: Returns a list of all hashed public keys in the crypto object register for the specified profile. The object result will contain the nine default keys(
app1,
app2, app3,
auth, cert
lisp,
network,
sign
and verify).