Indexing Status

Due to the fact that sometimes we have lots of transactions to process and that each integration's indexing complexity can vary, the client of the API should include the indexing status in the query to identify when the data is ready to be used.

The fields to query for are:

indexingStatus {
  headBlock // this is the block number we've identified as the lastest block in the blockchain
  headTimestamp // this is the timestamp of the headBlock above
  lastSyncedBlock // this is the block number that we sync-ed to for the wallet
  lastSyncedTimestamp // this is the timestamp of the lastSynchedBlock above
}

Please note that lastSyncedBlock can be lower than the current headBlock and if that's the case, that means the system is still indexing the user position.

Please also note that lastSyncedBlock can return -1, which means that there was a problem with the indexing of the user wallet.

📘

Please help us by filing a support ticket if you see issues such as a result of -1

For the latest entity information and schema please see the embedded tabs on the GraphQL endpoint: https://beta.archiveprotocol.com/graphql

Data example:

query {
  totalPositions(
    userIdentifier: "0x2f3890Fa27ec94EdAFb682D127C6d1CAA08EcbAe"
    blueprintId: "uniswap_v3_arbitrum"
  ) {
    requestId
    count
    activePositions
    positions
    indexingStatus {
      headBlock
      lastSyncedBlock
    }
  }
}

{
  "data": {
    "totalPositions": {
      "requestId": "413dd366-187b-59fa-98c5-3aade4f22aae",
      "count": 1,
      "activePositions": [
        "181090"
      ],
      "positions": [
        "181090"
      ],
      "indexingStatus": {
        "headBlock": 242180824,
        "headTimestamp": 1723488169,
        "lastSyncedBlock": 242180824,
        "lastSyncedTimestamp": 1723488169 
      }
    }
  }
}