Skip to main content
GET
Returns the stored bundle behind an asset data hash: the exact canonical bytes the hash commits to, and the same bundle as an object. This is what a lender of record reads before it acknowledges a version. It can recompute the hash from the bytes and compare it with the factory’s record, without trusting this response. The bytes are re-hashed before they leave. A stored row whose bytes no longer hash to their own key is refused with SNAPSHOT_CORRUPT rather than served as evidence. The hash on the factory still stands in that case, and the issuer is the party to ask for the bytes. Only bundles prepared through this platform are stored. A hash attested with bytes built elsewhere has nothing behind it here, and the call answers SNAPSHOT_NOT_FOUND. Get Asset Data says ahead of time whether bytes exist, as bundleAvailable. This endpoint takes the market’s contract address, not its market ID. The same audience as Get Asset Data can call it: see Who can read it.

Path Parameters

string
required
The market contract address, as 40 hex characters with a 0x prefix.

Query Parameters

string
The hash to read, as 0x and 64 hex characters. Omit it to read the attestation that stands on the factory now.
A hash can name any bundle stored for this market, including one stored by an Attest Asset Data build that was never signed. standing and version tell such a bundle apart from one that was attested.

Response Fields

object
standing and acknowledged both read false when the factory record could not be read. Check status on Get Asset Data before reading a false as a verdict.

Verify the bytes yourself

The check needs one hash function. Compare the result with attested on the factory record, which Get Asset Data returns as record.attested, or read assetData(market) on the factory directly.
TypeScript

Error Codes

The asset data routes report a validation failure with the first failing rule as message and no details list. Every access code from Get Asset Data applies here too.