Skip to main content
Holos uses webhooks to notify your infrastructure of platform events. Two webhook sources are active:
  • Stytch: identity and organization lifecycle events (member created, org updated, SSO configured)
  • Svix: platform-level events dispatched by the Holos API

​
Stytch webhooks

Stytch sends webhook payloads to the Holos API when identity events occur. These are used internally to keep the Holos member and organization records in sync with Stytch’s B2B data. If you need to react to member or org changes in your own systems, Stytch also supports outbound webhooks directly; configure them from the Stytch dashboard.

​
Svix webhooks

Holos uses Svix to dispatch platform events to external subscribers. Events are available for:
  • Capture lifecycle (created, uploaded, approved, rejected)
  • Skill updates
  • Object processing status changes
Webhook endpoints are configured per-organization. Contact your Holos admin to set up a webhook endpoint for your org.

​
Payload format

All webhook payloads are JSON. Each event has a type field and a data object: 
{
  "type": "capture.uploaded",
  "data": {
    "captureId": "cap_abc123",
    "organizationId": "org_xyz",
    "uploadedAt": "2026-05-12T20:00:00Z"
  }
}

​
Verification

Svix signs all webhook payloads with a secret specific to your endpoint. Verify the signature before processing the event. See the Svix verification docs for language-specific examples.