https://api.certo.bio/v1openapi.json

After the application: later events and a withdrawal

What your webhook hears after an application, what each event means for the copy you keep, and why the terms on the application are the ones to obey.

2 minute read

An application is the start: the candidate keeps working on their passport, sends you their checklist, and may withdraw. Your webhook hears each of these (Webhooks lists every event).

The events

EventWhat it means for you
request.submittedThe candidate sent you the application's checklist, or certo sent it because everything became ready. data.request.kind is application and data.request.id the application's id. Read the application again for what changed
application.withdrawnThe candidate withdrew the application. Same shape as application.submitted, state withdrawn
candidate.access_endedSent with it: your access to that candidate ended, reason withdrawn. candidate.id is the application's candidate_id

candidate.identity_verified is sent for candidates you invited or asked; it is not sent for an application. To see a candidate's identity check pass after they applied, watch for request.submitted and read candidate.identity on the application again.

A withdrawal

The candidate withdraws on Access or on the application's page, at any time, and does not need a reason. From then on GET /v1/applications/{id} answers grant.not_live, the candidate's passport no longer opens to you, and the application lists as withdrawn.

What you already copied: stop using it, and delete what the application's terms opened (the records, the contact details, the date of birth), unless you hold it on another basis of your own, such as the candidate's application in your ATS under your own privacy notice. The job's words, your state and your custom_data are yours.

A candidate who withdrew and applies again for the same job makes a new application, with a new id.

The terms are the snapshot to obey

Each application's terms say what it lets you read, as the candidate saw them on the consent screen, with their source: general, position or session. They do not follow later changes to the position or the general application. To ask an applicant for more, invite them or ask to read their passport: they approve that separately.

Reading again later

GET /v1/applications/{id} answers the application as it stands now, on its terms. GET /v1/candidates/{candidate_id} reads the same passport on the same access. Both are logged reads that the candidate sees. Neither costs a verification.