Skip to main content
GET
Track Data
Returns the track’s stored data record, exactly as the network holds it. What’s inside depends on the track’s kind (inline or coded). For an inline track, the record contains the bytes themselves. For a coded track, it contains the encoding record: the commitment material and coding parameters, not the decoded payload. That makes this endpoint a building block rather than a download. The SDK’s verified reads use it to fetch the material they check proofs against (verified reads). If you want the decoded payload, use get track or get object instead. Like the rest of the catalog family, the response arrives in the SDK’s binary encoding (conventions), so the practical way to consume it is through an SDK.

Example

The file holds the binary-encoded record. Decoding it by hand means reimplementing the SDK’s codec; there is rarely a reason to.