Webhooks

Webhooks let Equip push updates into your own systems the moment they happen. When a candidate’s assessment or AI interview attempt is fully graded, or a job application is created or changes stage in the ATS, Equip sends an HTTP POST request with a JSON payload to a URL you provide, so your CRM or internal tools stay in sync without polling.

If you only want results in a spreadsheet, use the no-code Write Results to Google Sheets option instead.

Setting Up a Webhook

Webhooks are configured at the team level. Your team has a single webhook URL, and every event you turn on is sent to it.

Prepare your endpoint

Set up an endpoint that accepts HTTP POST requests with a JSON body and responds within 10 seconds. Do any heavy processing asynchronously.

Add your URL

Enter your endpoint URL on the Developers page and save it.

Choose your events

Under Events, switch each event on or off. Saving a new URL turns on only assessment.completed and ai_interview.completed.

Verify with a real completion

Have a candidate complete an assessment or AI interview, or move an application to another stage, and confirm your endpoint receives the event.

Events

The two completion events fire once per candidate attempt, after grading is complete, so the scores in the payload are final. The two job application events come from the ATS.

Event	When it fires	On by default
`assessment.completed`	Every test in a candidate’s assessment attempt has been graded.	Yes
`ai_interview.completed`	A candidate’s AI interview attempt is fully graded.	Yes
`job_application.created`	A new application was created on a job opening.	No
`job_application.stage_changed`	An application moved to a different stage. Fires only when the stage actually changes.	No

An attempt that needs manual grading triggers its webhook only after you finalize the grade, not at submission time.

To call a URL from a pipeline stage’s automation rule, use the Notify an external system (webhook) automation action instead. It is set per stage and supports GET, POST, PUT and PATCH. See Automation Webhooks and External Updates.

Payloads

Every event uses the same envelope: the event type, a UTC timestamp in ISO 8601 format, and a data object with the event details.

{
  "event": "assessment.completed",
  "timestamp": "2026-07-25T09:30:00Z",
  "data": { ... }
}

assessment.completed

The data object contains:

Field	Description
`job_opening_label`	Identifier of the job opening.
`job_title`	Title of the job opening.
`candidate_email`	The candidate’s email address.
`candidate_name`	The candidate’s name.
`assessment_label`	Identifier of the assessment.
`assessment_report_url`	Link to the candidate’s detailed report on Equip.
`overall_score_percentage`	The candidate’s overall score as a percentage.
`started_at`	When the candidate started the attempt.
`finished_at`	When the candidate finished the attempt.
`hiring_status`	The candidate’s current hiring status.
`tests`	Array with one entry per test in the assessment.

Each entry in tests includes test_title, test_report_url, points_scored, points_available, and percentage_scored.

ai_interview.completed

The data object has the same fields as assessment.completed, with two differences:

ai_interview_label and ai_interview_report_url replace assessment_label and assessment_report_url.
There is no hiring_status or tests field.

job_application.created and job_application.stage_changed

The data object contains:

Field	Description
`job_application_id`	Identifier of the application.
`candidate_name`	The candidate’s name.
`candidate_email`	The candidate’s email address.
`job_opening_label`	Identifier of the job opening.
`job_title`	Title of the job opening.
`stage`	The application’s stage at the moment of the event: the starting stage for `job_application.created`, the new stage for `job_application.stage_changed`.
`application_source`	Where the application came from.
`applied_at`	When the application was created.
`actor_user_id`	The user who made the change.
`actor_name`	Full name of that user, or `null` when no user is recorded.

job_application.stage_changed also includes old_stage and new_stage.

Delivery Behavior

Deliveries are fire-and-forget: Equip sends each event once.

If your endpoint is down or takes longer than 10 seconds to respond, the event is not retried and is lost. If you miss an event, the results are still safe on Equip: open the candidate’s report on your dashboard, or pull results through the API.

API Integrations - Pull results and invite candidates programmatically
Write Results to Google Sheets - No-code alternative for exporting results
Automation Webhooks and External Updates - Per-stage webhooks from pipeline automation
Test Scores and Overall Score - How the scores in webhook payloads are calculated

ATS

Assessments

AI Interviews

Candidate Experience

Account & Billing

Setting Up a Webhook

Events

Payloads

assessment.completed

ai_interview.completed

job_application.created and job_application.stage_changed

Delivery Behavior

​Setting Up a Webhook

​Events

​Payloads

​assessment.completed

​ai_interview.completed

​job_application.created and job_application.stage_changed

​Delivery Behavior

​Related Resources

Setting Up a Webhook

Events

Payloads

assessment.completed

ai_interview.completed

job_application.created and job_application.stage_changed

Delivery Behavior

Related Resources