Webhooks

Webhooks connect Contents Capture to your other systems — a claims platform, a data warehouse, a notification service — in real time. When something happens here, we notify your endpoint immediately.

Outgoing webhooks

Register an endpoint and we'll POST a signed JSON payload whenever a subscribed event occurs.

Set one up

1. Open the org → Webhooks → Add endpoint.
2. Enter your URL.
3. Choose which events to subscribe to (or all).
4. Save. We show the signing secret once — copy it now and store it safely.

Events you can subscribe to

Assignment created / updated / status changed · invitation sent / accepted / revoked · room, group, person changes · media captured / uploaded · profile published, and more. (Full list mirrors the audit log.)

Verifying authenticity

Every delivery includes an X-CC-Signature header — an HMAC-SHA256 of the body using your signing secret. Your endpoint should recompute it and compare before trusting the payload.

IMPORTANT

Always verify the signature. It's how your system knows a payload genuinely came from Contents Capture and wasn't tampered with.

Deliveries & retries

We log every delivery and its result. Failed deliveries are retried with backoff; you can review recent deliveries (and failures) on the Webhooks screen. Respond 2xx quickly (do heavy work asynchronously) to keep deliveries healthy.

Incoming webhooks

You can also push data into Contents Capture from an external system — for example, your claim system creating context when a new claim opens. Incoming endpoints are authenticated per source; contact your implementation team to configure a source key.

TIP

Start by subscribing to media.uploaded and assignment.status_changed — together they let your downstream systems react the moment field work lands and when a job moves to review.

Next: Audit log.