Each fixture returned or referenced in the TxODDS Oracle API is part of an hourly batch of fixture updates. Blockchain holds the Merkle root (ultimate cryptographic containment proof) of each fixture belonging to that batch. This endpoint returns the Merkle proof, i.e., the hashes along the branch of the Merkle tree for the batch up to but not inclusive of that Merkle root. The user can then call on-chain validation directly to get a cryptographic validation that a given fixture update was published by TxODDS as confirmed by the published Merkle root. This on-chain transaction requires the fixture record and the Merkle proof returned here.
Documentation Index
Fetch the complete documentation index at: https://txline-docs.txodds.com/llms.txt
Use this file to discover all available pages before exploring further.
User's session JWT.
The user's long-lived API token, obtained from the activation endpoint.
Bearer token for the user's session JWT.
The user's long-lived API token.
The ID of the fixture to validate.
Optional. A Unix timestamp (ms) to get the validation proof for a specific point in time. Defaults to now.