Webhooks

A Memory webhook sends one memory.ready event after a Memory reaches its final processing stage. Create and manage subscriptions in Developer settings.

Configure a subscription

Each subscription has:

• an HTTPS endpoint URL without embedded credentials;
• a filter for all Memories or only accountant-relevant Memories;
• selected properties: type, source, metadata, Canonical Text, Description, Gist, Tags, Questions and relevance;
• a signing secret shown once when the subscription is created.

Memory ID and creation time are always included.

Event shape

{
  "event": "memory.ready",
  "deliveryId": "68f178a8-eaec-489f-bf73-b9948475af19",
  "occurredAt": "2026-09-11T09:42:19.000Z",
  "memory": {
    "id": "7b4f5c42-7f27-4f38-9f53-524b7e574d51",
    "createdAt": "2026-09-11T09:42:17.000Z",
    "gist": "Annual software subscription for £120 including VAT.",
    "tags": ["receipt", "software"],
    "relevance": { "relevant": true, "score": 0.98, "provenance": "model" }
  }
}

Delivery behavior

Return any 2xx response promptly. Network errors, 408, 425, 429 and 5xx responses are retried through Trace's durable delivery queue. Other responses are recorded as failed. A subscription pauses after 50 consecutive failures.

Retries can produce more than one HTTP request for the same event. Make the receiver idempotent by storing sterling-webhook-id or deliveryId before doing work.

Verify every signature before reading the payload.