Skip to content

Event Types

All webhook event types and when they fire.

PacSpace fires webhooks for key moments in the verification lifecycle. Subscribe to the events your application needs when creating a webhook.

Event Reference

EventDescriptionFires when
delta.verifiedA delta has been independently verifiedAfter each delta verification completes
delta.storedDelta hashes have been stored in the verification layerAfter storage confirmation
fact.verifiedA fact has been committed and verifiedAfter fact verification
checkpoint.verifiedA period-end checkpoint has been verifiedAfter checkpoint commitment
record.transferredA record ownership transfer is completeAfter transfer verification

Event Details

delta.verified

The most common event. Fires once for each delta after PacSpace completes verification. The payload includes the proof packet (proof hash, content hash, item hashes, chain link), the original delta context, verification results, and optional period and usage information.

Use this event to:

  • Confirm your delta was recorded correctly
  • Store the proof hash for your own audit trail
  • Trigger downstream workflows (invoicing, reconciliation, notifications)

See the full payload schema.

delta.stored

Fires when delta hashes have been permanently stored in PacSpace's verification layer. The payload includes the start index, count, and verification confirmation. This event confirms that the proof data is committed and immutable.

Use this event to:

  • Log storage confirmations
  • Update internal status from "verifying" to "stored"

fact.verified

Fires when an individual fact has been committed and verified. The payload includes the content hash, proof hash, and verification confirmation. Facts are discrete data points associated with a record (as opposed to deltas, which represent changes).

Use this event to:

  • Confirm fact data integrity
  • Trigger downstream processing that depends on verified facts

checkpoint.verified

Fires when a period-end checkpoint has been committed and verified. The payload includes the range of delta indexes covered (fromIndex, toIndex), the proof hash, and a message recommending you include the proof hash in invoices.

Use this event to:

  • Generate period-end reports
  • Include the proof hash in invoices for counterparty verification
  • Archive period data with a verified proof

record.transferred

Fires when ownership of a record has been transferred from one party to another and the transfer has been verified. The payload includes the receipt ID and verification confirmation.

Use this event to:

  • Update internal ownership records
  • Notify relevant parties about the transfer
  • Trigger post-transfer workflows

Subscribing to Events

When creating a webhook, specify which events you want to receive in the events array:

bash
curl -X POST https://balance-api.pacspace.io/dashboard/webhooks \
  -H "Authorization: Bearer YOUR_JWT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://your-app.com/webhooks"
  }'

Note: Webhooks currently receive all event types. Event filtering is not yet supported in the create webhook API — all configured endpoints receive every event.

Event Envelope

Every webhook delivery uses the same envelope structure:

json
{
  "event": "delta.verified",
  "timestamp": "2026-02-11T10:30:00Z",
  "data": {
    // ... event-specific payload
  }
}
FieldTypeDescription
eventstringThe event type identifier
timestampstringISO 8601 timestamp of when the event occurred
dataobjectEvent-specific payload (see Payload Reference)

Next Steps