Tables

Get table item

Changed on Oct 9, 2025

Get a table item at a specific ledger version from the table identified by {table_handle} in the path and the "key" (TableItemRequest) provided in the request body.

This is a POST endpoint because the "key" for requesting a specific table item (TableItemRequest) could be quite complex, as each of its fields could themselves be composed of other structs. This makes it impractical to express using query params, meaning GET isn't an option.

The Lumio nodes prune account state history, via a configurable time window. If the requested ledger version has been pruned, the server responds with a 410.

post/tables/{table_handle}/item

Request

Base URL
/v1 (relative, and the document was published on a file host, not at the API’s origin)
URL
/v1/tables/{table_handle}/item
Auth
none declared

Path parameters

table_handlestring hex required

A hex encoded 32 byte Lumio account address.

This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.

For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.

Table handle hex encoded 32-byte string

Query parameters

ledger_versionstring uint64

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

Example:32425224034

Ledger version to get state of account

If not provided, it will be the latest version

Request body

key_typestring required

String representation of an on-chain Move type tag that is exposed in transaction payload. Values: - bool - u8 - u16 - u32 - u64 - u128 - u256 - address - signer - vector: vector<{non-reference MoveTypeId}> - struct: {address}::{module_name}::{struct_name}::<{generic types}>

Vector type value examples:
  - `vector<u8>`
  - `vector<vector<u64>>`
  - `vector<0x1::coin::CoinStore<0x1::lumio_coin::LumioCoin>>`

Struct type value examples:
  - `0x1::coin::CoinStore<0x1::lumio_coin::LumioCoin>
  - `0x1::account::Account`

Note:
  1. Empty chars should be ignored when comparing 2 struct tag ids.
  2. When used in an URL path, should be encoded by url-encoding (AKA percent-encoding).

value_typestring required

Vector type value examples:
  - `vector<u8>`
  - `vector<vector<u64>>`
  - `vector<0x1::coin::CoinStore<0x1::lumio_coin::LumioCoin>>`

Struct type value examples:
  - `0x1::coin::CoinStore<0x1::lumio_coin::LumioCoin>
  - `0x1::account::Account`

Note:
  1. Empty chars should be ignored when comparing 2 struct tag ids.
  2. When used in an URL path, should be encoded by url-encoding (AKA percent-encoding).

keyunknown required

Response

MoveValue required

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 Lumio 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 value 0x1::string::String{bytes: b"Hello World!"} is serialized as "Hello World!" in JSON.

Example response

{
  "authentication_key": "0x0000000000000000000000000000000000000000000000000000000000000001",
  "coin_register_events": {
    "counter": "0",
    "guid": {
      "id": {
        "addr": "0x1",
        "creation_num": "0"
      }
    }
  },
  "self_address": "0x1",
  "sequence_number": "0"
}

Changes

Oct 9, 20255bfbbc5f3ce7 Revision changes
- breaking
  the mandatory response header X-APTOS-BLOCK-HEIGHT removed for the status 200
- breaking
  the mandatory response header X-APTOS-CHAIN-ID removed for the status 200
- breaking
  the mandatory response header X-APTOS-EPOCH removed for the status 200
- breaking
  the mandatory response header X-APTOS-LEDGER-OLDEST-VERSION removed for the status 200
- breaking
  the mandatory response header X-APTOS-LEDGER-TIMESTAMPUSEC removed for the status 200
- breaking
  the mandatory response header X-APTOS-LEDGER-VERSION removed for the status 200
- breaking
  the mandatory response header X-APTOS-OLDEST-BLOCK-HEIGHT removed for the status 200
- warning
  the optional response header X-APTOS-BLOCK-HEIGHT removed for the status 400
- warning
  the optional response header X-APTOS-BLOCK-HEIGHT removed for the status 403
- warning
  the optional response header X-APTOS-BLOCK-HEIGHT removed for the status 404
- warning
  the optional response header X-APTOS-BLOCK-HEIGHT removed for the status 410
- warning
  the optional response header X-APTOS-BLOCK-HEIGHT removed for the status 500
- warning
  the optional response header X-APTOS-BLOCK-HEIGHT removed for the status 503
- warning
  the optional response header X-APTOS-CHAIN-ID removed for the status 400
- warning
  the optional response header X-APTOS-CHAIN-ID removed for the status 403
- warning
  the optional response header X-APTOS-CHAIN-ID removed for the status 404
- warning
  the optional response header X-APTOS-CHAIN-ID removed for the status 410
- warning
  the optional response header X-APTOS-CHAIN-ID removed for the status 500
- warning
  the optional response header X-APTOS-CHAIN-ID removed for the status 503
- warning
  the optional response header X-APTOS-CURSOR removed for the status 200
- warning
  the optional response header X-APTOS-EPOCH removed for the status 400
- warning
  the optional response header X-APTOS-EPOCH removed for the status 403
- warning
  the optional response header X-APTOS-EPOCH removed for the status 404
- warning
  the optional response header X-APTOS-EPOCH removed for the status 410
- warning
  the optional response header X-APTOS-EPOCH removed for the status 500
- warning
  the optional response header X-APTOS-EPOCH removed for the status 503
- warning
  the optional response header X-APTOS-GAS-USED removed for the status 200
- warning
  the optional response header X-APTOS-GAS-USED removed for the status 400
- warning
  the optional response header X-APTOS-GAS-USED removed for the status 403
- warning
  the optional response header X-APTOS-GAS-USED removed for the status 404
- warning
  the optional response header X-APTOS-GAS-USED removed for the status 410
- warning
  the optional response header X-APTOS-GAS-USED removed for the status 500
- warning
  the optional response header X-APTOS-GAS-USED removed for the status 503
- warning
  the optional response header X-APTOS-LEDGER-OLDEST-VERSION removed for the status 400
- warning
  the optional response header X-APTOS-LEDGER-OLDEST-VERSION removed for the status 403
- warning
  the optional response header X-APTOS-LEDGER-OLDEST-VERSION removed for the status 404
- warning
  the optional response header X-APTOS-LEDGER-OLDEST-VERSION removed for the status 410
- warning
  the optional response header X-APTOS-LEDGER-OLDEST-VERSION removed for the status 500
- warning
  the optional response header X-APTOS-LEDGER-OLDEST-VERSION removed for the status 503
- warning
  the optional response header X-APTOS-LEDGER-TIMESTAMPUSEC removed for the status 400
- warning
  the optional response header X-APTOS-LEDGER-TIMESTAMPUSEC removed for the status 403
- warning
  the optional response header X-APTOS-LEDGER-TIMESTAMPUSEC removed for the status 404
- warning
  the optional response header X-APTOS-LEDGER-TIMESTAMPUSEC removed for the status 410
- warning
  the optional response header X-APTOS-LEDGER-TIMESTAMPUSEC removed for the status 500
- warning
  the optional response header X-APTOS-LEDGER-TIMESTAMPUSEC removed for the status 503
- warning
  the optional response header X-APTOS-LEDGER-VERSION removed for the status 400
- warning
  the optional response header X-APTOS-LEDGER-VERSION removed for the status 403
- warning
  the optional response header X-APTOS-LEDGER-VERSION removed for the status 404
- warning
  the optional response header X-APTOS-LEDGER-VERSION removed for the status 410
- warning
  the optional response header X-APTOS-LEDGER-VERSION removed for the status 500
- warning
  the optional response header X-APTOS-LEDGER-VERSION removed for the status 503
- warning
  the optional response header X-APTOS-OLDEST-BLOCK-HEIGHT removed for the status 400
- warning
  the optional response header X-APTOS-OLDEST-BLOCK-HEIGHT removed for the status 403
- warning
  the optional response header X-APTOS-OLDEST-BLOCK-HEIGHT removed for the status 404
- warning
  the optional response header X-APTOS-OLDEST-BLOCK-HEIGHT removed for the status 410
- warning
  the optional response header X-APTOS-OLDEST-BLOCK-HEIGHT removed for the status 500
- warning
  the optional response header X-APTOS-OLDEST-BLOCK-HEIGHT removed for the status 503
Jun 3, 20256a8502f67ac1 Revision changes
- warning
  added the new rejected_by_filter enum value to the response property for the response status
- warning
  added the new rejected_by_filter enum value to the response property for the response status
- warning
  added the new rejected_by_filter enum value to the response property for the response status
- warning
  added the new rejected_by_filter enum value to the response property for the response status
- warning
  added the new rejected_by_filter enum value to the response property for the response status
- warning
  added the new rejected_by_filter enum value to the response property for the response status

Operation history (4 revisions)