Overview
AI Apply is asynchronous by design (form parsing and applications are long-running processes that run in the background). To keep your system in sync without polling, we emit webhooks whenever a resource reaches a meaningful outcome.First time implementing Kombo webhooks?View our general Webhooks guide for more information on
delivery, signature validation, and other generic behaviors.
Job Posting Updated Webhook
Lifecycle
Status | Emits webhook? | Description |
---|---|---|
PENDING | ❌ | Parsing is queued/processing |
APPLYABLE | ✅ | Kombo has successfully parsed the job posting. You can submit applications |
UNAVAILABLE | ✅ | Parsing the job posting failed |
ARCHIVED | ✅ | The job was taken offline or manually archived |
If a parse attempt fails but a previous successful revision still exists, the
posting remains
APPLYABLE
.Payload
The payload matches the job posting schema you receive from the get job posting endpoint. Examples- A job posting was successfully parsed.
- A job posting failed to parse.
- A job posting was taken offline.
Handling job posting availability changes
A job posting’savailability
field may switch from being non-applyable to applyable, and vice versa.
As soon as this changes, you should update your UI accordingly.
We recommend either hiding the job from the list of jobs you display to candidates or showing the job URL directly for the candidate to apply on the career site.
Most transitions from being applyable to non-applyable are caused by a job
posting being archived. In rare cases, a job posting’s application form may
change, triggering a re-parse.
Application Updated Webhook
Lifecycle
Status | Emits webhook? | Description |
---|---|---|
PENDING | ❌ | Our automated system is applying or the application is pending manual review |
SUBMITTED | ✅ | The application was successfully submitted |
FAILED | ✅ | The application was deemed impossible to submit after human review |
When can an application be marked as
FAILED
?If the candidate input is fundamentally invalid, and Kombo has no chance to
submit the application in the candidate’s name without the candidate providing
more information, the application will be marked as failed. In the future, Kombo
may support flows of following up with the candidate to collect remaining data
in an automated manner.In rare edge cases, when a job is taken offline while an application is
in-flight, the application will also be marked as failed.Payload
The payload follows the application schema you receive from the get application endpoint. Examples- Application is automatically submitted
- Application is submitted after Kombo QA
- Application is marked as failed by Kombo QA (e.g., invalid candidate input)