Skip to content

Commit 33b14fb

Browse files
Update docs/sdk-and-tools/rest-api/iterate-keys.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent 42d72e3 commit 33b14fb

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/sdk-and-tools/rest-api/iterate-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ This endpoint will only work if the node's `config.toml` file has the following
144144
- The `pairs` object contains hex-encoded keys and values. Decode as needed.
145145
- Always pass `newIteratorState` as-is in your next request's `iteratorState` field to continue iteration.
146146
- When `newIteratorState` is null, all keys have been retrieved.
147-
- If `iteratorState` is empty in the request, iteration starts from the beginning of the trie.
147+
- If `iteratorState` is an empty array (`[]`) in the request, iteration starts from the beginning of the trie.
148148
- If `numKeys` is 0, the server will return as many keys as possible until all are retrieved or until the `TrieOperationsDeadlineMilliseconds` timeout is reached.
149149
- If retrieving `numKeys` takes more time than the timeout, the request will return the keys collected up to that point.
150150
- Use `?blockNonce={blockNonce}` to ensure all requests iterate the same trie root, even if the account changes between requests.

0 commit comments

Comments
 (0)