Skip to content
Documentation

Webhooks

Updated 14 August 2026

/output-integrations/webhooks

Webhooks

Webhooks are how TechWolf tells an organisation's systems that something has changed, the moment it changes. TechWolf sends a notification to an endpoint the organisation exposes. The notification says what changed, for example which employee's skill profile was updated, so the receiving system knows what to act on and can fetch the new data.

That is what lets an organisation build real-time integrations and automations on TechWolf data: each change triggers the work, and only the data that changed is revisited.

Key attributes

Event types
Notifications cover changes to employee, job, and course skill profiles, with validated profiles and newly suggested skills carried as separate event types, and changes to the skill vocabulary and the organisation's taxonomy. A consumer subscribes only to the event types it needs, and every registered endpoint also answers a health-check event that TechWolf uses to confirm the endpoint is live.
Thin events
Each notification signals that something changed and for which entity, and the changed data itself always comes from the SkillEngine API. That keeps the API the single authoritative source: since a notification can arrive more than once and out of order, a copy of the data travelling with it could already be out of date on arrival.
Delivery
One notification is sent per request, and is delivered at least once, without a guaranteed order. A failed delivery is retried, with increasing backoff time between retries. Consumers deduplicate by event identifier and process each event idempotently, so a repeated notification has the same effect as a single one.
Security
Every notification carries an Ed25519 signature and a timestamp, which the consumer verifies before acting on it. Optionally, OAuth 2.0 or a key in an HTTP header can be used to authenticate with the organisation's endpoint.

How it works

The organisation exposes an HTTPS endpoint and registers it with TechWolf, together with the event types it wants to receive. When a subscribed change happens, TechWolf sends the notification in the CloudEvents format; the consumer verifies it, acknowledges receipt, and fetches the changed resource from the SkillEngine API.

Webhooks make changes visible in near real time. A scheduled reconciliation alongside them is what keeps two systems aligned: it re-reads both sides, settles any difference, and closes the gap left when an endpoint was unavailable for the whole of a delivery's retries. A notification signals that something changed, not what the change was. The current state, and the history behind a profile, come from the SkillEngine API.

The event reference, delivery protocol, and signature verification are documented in TechWolf's developer documentation.

Prerequisites

Webhooks are part of TechWolf's output integrations. They require an HTTPS endpoint operated by the organisation and SkillEngine API access to fetch the changed resources. TechWolf sends webhooks from a fixed set of IP addresses per region. If the organisation's network filters inbound traffic, the organisation must allowlist the addresses for its region.

Availability

  • Console: webhooks are configured and tested in the Console, as an outbound integration in the Integration Manager.