Webhooks

API credentials let your system ask Knowspread questions. Webhooks are the other direction: the space tells your system when something happens, without being asked.

The screen

123

Webhook settings with the event catalogue open

1. One endpoint receives everything. You give its URL and a secret — Vygenerovat secret produces one for you (1).
2. Auth type is separate from the secret and defaults to none (2). Basic auth credentials appear once you pick it.
3. Subscriptions are added one event at a time, each with a schema version (3). Nothing is subscribed by default.

The events on offer

The picker offers four events, and they are about assignments and tests rather than about people or content changing.

Event	Fires when
content_assignment_created	Content is assigned to someone
content_assignment_completed	Someone finishes assigned content
content_assignment_overdue	An assignment passes its deadline
test_attempt_completed	Someone finishes a test attempt

Each subscription carries a schema version — v1.0 is what the version picker offers — so the payload shape is versioned separately from the event name.

The secret is a signature, not a password

Basic auth is separate and optional — it authenticates the call at the transport level, where the secret authenticates the payload.

What to watch for

In a personal space this screen draws the form but nothing behind it is live: webhooks, webhook_settings and webhooks/pending_requests all answer 403. The subscription section stays empty because it was refused, not because nothing is subscribed.