# Status Check

Status Changes

Because of the timestamping interval and blockchain network times, we cannot exactly predict when a timestamp will become tamper-proof. Polling the API for tree status updates is discouraged. Instead, rely on automatic webhook notifications as explained in the verification section.

If the hash has been linked to a verified Merkle Tree and blockchain, you can query the status of said tree with the treeId field by which the hash is linked. The response will include details about the transaction and blockchain used.

Information on how to send a status request in our API Reference (opens new window).

An example response looks as follows:

{
  "treeId": "4dc4c401-5a55-48ee-802c-3f1659b10aa5",
  "currencyId": 0,
  "currency": "BTC",
  "submitStatus": 3,
  "timestamp": 1710000000000,
  "rootSha256": "dc19dddc4e9f8742e31cbbaafe894daa01760f32b11d5cce29224981cef4ba1b",
  "transaction": "9f2c93c0edc444f17e6a96c771f34243c0978be4cf90c5d33bb8bfb5a1e5a4f3"
}

If the tree is not yet verified, the submitStatus will be less than 3 and the transaction-related information will be missing.

{
  "treeId": "4dc4c401-5a55-48ee-802c-3f1659b10aa5",
  "currencyId": 0,
  "currency": "BTC",
  "submitStatus": 0,
}

# currencyId

The ID of the blockchain currency used for the timestamp. For example, 0 for Bitcoin (BTC), 1 for Ethereum (ETH). This is also presented in human-readable form in the currency field.

# rootSha256

The rootSha256 represents the top hash in the Merkle Tree. Synonyms: root hash, private key, top hash, seed hash.

# submitStatus

ID Status Description
0 unsubmitted The hash is assigned, but the Merkle Tree has not been created yet. This is the initial state.
1 submitted The hash was included into a transaction and broadcast to the network, but not included in a block.
2 included The transaction was included into the latest block.
3 verified The timestamp for your hash was successfully created and permanently included in the blockchain.

# timestamp

The tamper-proof timestamp of all hashes contained in this tree. It is formatted as follows:

[ms] since 1.1.1970 (unix epoch), timezone: UTC

# transaction

The transaction ID of the timestamp, e.g., a transaction hash in Bitcoin.