Receipts

GET /api/v1/records/{recordType}/{record}/receipts/{seq}

A receipt is one committed entry, on its own. It carries the sealed record exactly as it was committed, the seal, and what a check needs to compare the two. The history carries every receipt at once; fetch a single receipt when you hold an entry number from the record.committed webhook and want just that entry.

Call#

const { receipt } = await pac.records.receipt({ record: 'build-2026-09-15-0417', entry: 1 });   // the first entry

What comes back#

{
  "success": true,
  "data": {
    "recordType": "machine-action-record",
    "entityId": "build-2026-09-15-0417",
    "receipt": { "...": "the committed entry, its seal, and what the check needs" },
    "verify": { "...": "where the record was committed, for a check that reads the public source" }
  }
}

Inside receipt, the part you read is the sealed record: the title, occurredAt, actorId, payloads, and whatever else you sent, exactly as committed. The rest of the receipt is what a check consumes, and its shape belongs to the checker. Read it with records.check or the standalone checker rather than by hand.

Entries count from 1 in the SDKs and on every page: entry: 1 is the first entry, the one the record page calls Entry 1. On the wire the same position is seq, counted from 0, so the path for the first entry ends in /receipts/0 and seq is entry - 1; the SDKs convert for you and refuse an entry below 1 before anything is sent. The number comes from the record.committed webhook (records[].seq) or from the history; the write's own answer does not carry it, because the number is assigned when the entry commits.

Who can read it#

Your workspace's key, or a grant token for this record sent as ?grant=. A person on the other side does not need either; the Shared Record shows them each entry.

When the call is refused#