> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tape.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Track Data

> Fetch a track's stored data record through the versioned catalog API.

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](/protocol/architecture/tracks)). 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](/sdks/reading)). If you want the decoded payload, use [get track](/apis/gateway/tracks/get-track) or [get object](/apis/gateway/objects/get-object) instead.

Like the rest of the catalog family, the response arrives in the SDK's binary encoding ([conventions](/apis/gateway)), so the practical way to consume it is through an SDK.

## Example

```bash theme={null}
curl -s -o track-record.bin "$TAPE_GATEWAY/v1/tracks/7f3kD9mQxYz2pW8vN4cRtE5uH6bJamd9GvKq2rTeUWXs/data"
```

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