Path Parameters
Table handle hex encoded 32-byte string
"0xc739507214d0e1bf9795485299d709e00024e92f7c0d055a4c2c39717882bdfd"
Query Parameters
Ledger version to get state of account
If not provided, it will be the latest version
"32425224034"
Body
Table Item request for the GetTableItemRaw API
All bytes (Vec<u8>) data is represented as hex-encoded string prefixed with 0x
and fulfilled with
two hex digits per byte.
Unlike the Address
type, HexEncodedBytes will not trim any zeros.
"0xc739507214d0e1bf9795485299d709e00024e92f7c0d055a4c2c39717882bdfd"
Response
An enum of the possible Move value types This is a JSON representation of some data within an account resource. More specifically, it is a map of strings to arbitrary JSON values / objects, where the keys are top level fields within the given resource.
To clarify, you might query for 0x1::account::Account and see the example data.
Move bool
type value is serialized into boolean
.
Move u8
, u16
and u32
type value is serialized into integer
.
Move u64
, u128
and u256
type value is serialized into string
.
Move address
type value (32 byte Aptos account address) is serialized into a HexEncodedBytes string.
For example:
0x1
0x1668f6be25668c1a17cd8caf6b8d2f25
Move vector
type value is serialized into array
, except vector<u8>
which is serialized into a
HexEncodedBytes string with 0x
prefix.
For example:
vector<u64>{255, 255}
=>["255", "255"]
vector<u8>{255, 255}
=>0xffff
Move struct
type value is serialized into object
that looks like this (except some Move stdlib types, see the following section):
{
field1_name: field1_value,
field2_name: field2_value,
......
}
For example:
{ "created": "0xa550c18", "role_id": "0" }
Special serialization for Move stdlib types:
- 0x1::string::String
is serialized into
string
. For example, struct value0x1::string::String{bytes: b"Hello World!"}
is serialized as"Hello World!"
in JSON.