extraction.updated
Fires when a stored extraction is rewritten in place after extraction.ready already fired for that document: what you fetched is stale. Re-fetch and compare extraction_version against previous_extraction_version.
Fires when a stored extraction is rewritten in place after extraction.ready already fired for that document: what you fetched is stale. Re-fetch and compare extraction_version against previous_extraction_version.
Signature over the exact request body: t=<seconds since the Unix epoch>,v1=<lowercase hex HMAC-SHA256 of "{t}.{body}" keyed with your endpoint's signing secret>. Verify it before trusting the body, and reject a t more than five minutes from your own clock. During a secret rotation both the new and the previous secret verify for 24 hours; each delivery is signed with exactly one.
The event id, identical to the body’s id. Stable across retries and replays, and shared by every endpoint one event fans out to. Delivery is at-least-once, so dedupe on it.
Event id: evt_ plus 24 lowercase hex characters. Also sent as the SpreadSpace-Event-Id header. Stable across retries and replays, so dedupe on it.
Seconds since the Unix epoch at which the event was created server-side. Seconds, not milliseconds. Deliveries are not ordered; reconcile on this.
true for live activity, false for test mode (an ss_test_ key or the sandbox simulator). Branch on it to route test deliveries to a staging handler.
The data object on an extraction.updated delivery, sent when a
stored extraction is rewritten after extraction.ready already fired
for that document. What you fetched on ready is now stale: re-fetch
the document, and the new read carries extraction_version. Today the
only cause is an enrichment landing after the ready grace window.
Identifiers only: no figures and no personal data, like every sibling payload.