> This page is for API.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.spreadspace.app/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.spreadspace.app/_mcp/server.

# job.completed

POST 

Terminal event for a document package: fires exactly once, when every document in it has reached a terminal state, success or failure.

Reference: https://docs.spreadspace.app/api/api-reference/webhook-events/webhook-job-completed

## Request

### Headers

- `SpreadSpace-Signature` (string, required) — 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.
- `SpreadSpace-Event-Id` (string, required) — 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.

### Payload

- `id` (string, required) — 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.
- `type` (enum, required) — Always this event type on this body.
  - Allowed values: `job.completed`
- `created` (long, required) — Seconds since the Unix epoch at which the event was created server-side. Seconds, not milliseconds. Deliveries are not ordered; reconcile on this.
- `tenant_id` (string, required) — The workspace the event belongs to. Reject a delivery whose tenant does not match the endpoint you registered.
- `livemode` (boolean, required) — `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.
- `data` (JobCompletedPayload, required) — The `data` object on a `job.completed` delivery, the terminal event for a document package. Sent exactly once, when every document in it has reached a terminal state, success or failure. Most integrators trigger downstream work from this event rather than from the per-document ones. The three counts are authoritative: succeeded plus failed can briefly disagree with the total while a package is still settling.

## Types

### JobCompletedPayload

The `data` object on a `job.completed` delivery, the terminal event for a document package. Sent exactly once, when every document in it has reached a terminal state, success or failure. Most integrators trigger downstream work from this event rather than from the per-document ones. The three counts are authoritative: succeeded plus failed can briefly disagree with the total while a package is still settling.

- `job_id` (string, required) — The document package (job) that finished.
- `borrower_id` (string, required) — The borrower that owns the loan.
- `loan_id` (string, required) — The loan the package was uploaded against.
- `document_count_total` (integer, required) — Total documents in the package.
- `document_count_succeeded` (integer, required) — Documents that reached a terminal success state.
- `document_count_failed` (integer, required) — Documents that terminated in failure.
- `completed_at` (datetime, required) — Server-side wall-clock time the job entered its terminal state.