Praxicraft Assess — hiring workspace docs

A webhook is an HTTPS URL Assess calls when something happens. Your tool (n8n, Zapier, Make, or your backend) listens and reacts. no need to refresh the dashboard. Destinations (HTTPS, Slack, Teams) are the same Public API surface: /webhooks/: There is no separate /destinations/ path.

If you are recruiting / ops

You usually do not configure webhooks by hand. Instead:

Ask engineering to register your automation URL, or
Use the n8n Assess node, Zapier, or Make app. they register the webhook when the scenario/workflow is active, or
Follow Automations for a custom catch hook

Useful events to ask for:

Event	Plain meaning
`assessment.completed`	Candidate finished the test
`candidate.passed` / `failed`	Score vs passing score
`invitation.created`	New assessment invite created
`job.published` / `closed`	Opening went live or closed
`application.submitted` / `screened`	Apply received or CV screen finished
`application.advanced` / `rejected`	Recruiter decision on an application
`application.hired`	Marked hired (optional soft offer follows)
`offer.sent` / `accepted` / `declined` / `withdrawn`	Soft offer lifecycle
`candidate.updated` / `note_added` / `merged`	CRM profile changes (not assessment pass/fail)
`candidate.pool_added`	Added to talent pool
`pipeline.enrolled` / `advanced` / `held` / `unheld`	Funnel movement
`interview.completed` / `no_show`	Live interview ended or expired

Sample JSON for each event: Webhook events.

For engineers

Register an HTTPS endpoint. You receive a whsec_… secret once to verify X-Praxicraft-Signature. Live destinations only receive live events. Create a separate destination in Test mode (or with a ct_test_ key) while you debug. test candidate.passed never hits a live URL. See Live and Test mode.

Endpoints

Method	Path	Scope
GET	`/webhooks/`	`webhooks:read`
POST	`/webhooks/create/`	`webhooks:write`
GET / PATCH / DELETE	`/webhooks/{id}/`	read / write
GET	`/webhooks/{id}/deliveries/`	`webhooks:read`
POST	`/webhooks/{id}/deliveries/{delivery_id}/retry/`	`webhooks:write`
POST	`/webhooks/{id}/test/`	`webhooks:write`

Create and verify

Body uses events (not event_types):

curl -sS -X POST https://assess.praxicraft.com/api/v1/public/webhooks/create/ \
 -H "Authorization: Bearer $PRAXICRAFT_API_KEY" \
 -H "Content-Type: application/json" \
 -d '{
 "url": "https://example.com/hooks/praxicraft",
 "events": ["assessment.completed", "candidate.passed"]
 }'

Store secret_key. Then:

curl -sS -X POST \
 "https://assess.praxicraft.com/api/v1/public/webhooks/WEBHOOK_ID/test/" \
 -H "Authorization: Bearer $PRAXICRAFT_API_KEY"

HTTP 2xx on the test ping sets is_verified and is_active.

Slack or Teams (no HMAC)

For “candidate passed → hiring channel”, use a chat destination instead of a signed HTTPS URL:

Slack. Connect Slack or Incoming Webhook
Microsoft Teams. Incoming Webhook connector

Assess posts a formatted chat message (not the signed JSON envelope). HTTPS destinations still use whsec_… and X-Praxicraft-Signature. Failed deliveries can be resent from Developer → Events (filter Failed) or:

curl -sS -X POST \
 "https://assess.praxicraft.com/api/v1/public/webhooks/WEBHOOK_ID/deliveries/DELIVERY_ID/retry/" \
 -H "Authorization: Bearer $PRAXICRAFT_API_KEY"

Signature

X-Praxicraft-Signature: sha256=<hex>

HMAC-SHA256 of the raw body with whsec_…. Helpers: SDK webhooks.

Debugging deliveries

Failed rows live in Developer → Events (filter Failed) and on each destination’s delivery log.

What you see	What to do
Last payload	Open the event. Event data is the JSON Assess sent (or the chat card for Slack/Teams).
HTTP 4xx/5xx + response body	The destination answered. Fix the listener, then Resend.
HTTP 401 / 403	Often HMAC: verify the raw body with `whsec_…` in the signature playground.
Timeout / connection error	URL unreachable. Check TLS, firewall, and that the host is public.
Auto-paused	Health probes failed. Fix the URL, send a test ping, pending rows replay.

GET /webhooks/{id}/deliveries/ now includes payload, last_error, response_status_code, and a truncated response_body.

Full event list

Every event name and a sample JSON body: Webhook events. Subscribe with any of: assessment.started, assessment.completed, candidate.passed, candidate.failed, candidate.violation, invitation.created, invitation.expired, pipeline.enrolled, pipeline.advanced, pipeline.completed, pipeline.rejected, pipeline.held, pipeline.unheld, interview.scheduled, interview.started, interview.completed, interview.cancelled, interview.no_show, interview.analysis_ready, webhook.test.

Delivery behaviour

Retries on 5xx/timeout: up to 3 (~1m, 2m, 4m)
4xx = no retry
Deduplicate with delivery id / event_id

Webhook event samples · SDK verification · Slack · Teams · Integrations · Automations

Jobs & screening

Assessments

Interviews & pipelines

Webhooks

Account & reference

Webhooks

If you are recruiting / ops

For engineers

Endpoints

Create and verify

Slack or Teams (no HMAC)

Signature

Debugging deliveries

Full event list

Delivery behaviour

Next

​If you are recruiting / ops

​For engineers

​Endpoints

​Create and verify

​Slack or Teams (no HMAC)

​Signature

​Debugging deliveries

​Full event list

​Delivery behaviour

​Next

If you are recruiting / ops

For engineers

Endpoints

Create and verify

Slack or Teams (no HMAC)

Signature

Debugging deliveries

Full event list

Delivery behaviour

Next