Quick Summary: The v1 API does not deliver webhooks. Detect changes by polling the activity feeds on a schedule, filtered by date, and send an
Idempotency-Key on any write your poller triggers.No webhooks
There is no webhook or event-subscription mechanism in v1 — SkillsDB never calls your systems. If your integration needs to react to changes, poll for them.Polling the activity feeds
Two resources expose an activity feed:
The career feed accepts
from and to (ISO 8601 UTC) plus event and performedBy filters. Poll it by remembering when you last polled and asking only for what is new:
from. Overlap the windows slightly and deduplicate on the entry id rather than trusting an exact boundary.
The skill feed is a version log (baseline, version_created, renew_training) with pagination only — no date filter. Each entry carries performedAt; page through and stop when you reach entries you have already seen.
Keep the poller polite
Polls are GETs, counted against the reads bucket — 1,000 per hour per key. WatchRateLimit-Remaining and size your interval so a full sweep fits comfortably.
If a poll result triggers a write back into SkillsDB, send an Idempotency-Key from day one — a poller that crashes mid-run and restarts will otherwise perform its writes twice.