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

Apply with certo: which recipe is yours

A button on a job page that sends you a candidate's certo passport, free. The three ways to set it up, how to choose, and what all three share.

4 minute read

Apply with certo puts a button on a job page: your careers site, a job board, an ATS's hosted page. The candidate presses it and certo opens in a popup. They sign in (or make a passport there, from their CV), read who receives what, and press Apply. Your organisation can then read what they sent, at no cost to you or to them, and the application reaches you as signed JSON in the page, through your webhook and the API, or both.

These pages are the integrator's cookbook. Setting it up in the console is in Apply with certo integration.

The three recipes

The terms of an application are what it lets you read and what the candidate should have ready: scope_types, include_contact, include_birth_date with birth_date_reason, and requirements, the same fields a position or an invitation carries. They come from exactly one place, named by the id the button opens with.

a) General applicationb) Apply sessionc) Position
The idao_ and 32 hex charactersas_ and 32 hex charactersap_ and 32 hex characters
Terms fromYour general application, saved under IntegrationsYour server's call to POST /v1/apply-sessions, then its position's terms, then the general onesThe position
A call per clickNoneOne, from your server to certoNone
ReusableEvery candidateOne candidate, once, within an hourEvery candidate
Filed under a positionNo (a recruiter may move it later)When the session names oneYes
The job's wordsFrom the buttonFrom the session onlyThe position's title; job_ref from the button
terms.sourcegeneralsessionposition

Which one is yours

  1. Do your jobs live in certo as positions? Use recipe c, a position: switch the position on and paste its button. Closing the position closes its button.
  2. Do you need different terms per job or per candidate, or do you list thousands of jobs that are not positions in certo? Use recipe b, apply sessions. It needs a server that calls the API.
  3. Neither? Use recipe a, the general application: one set of terms, a button with the job's words on it, or none at all for an open application to your company.

You may mix them: the general application on a job board, positions on your own careers site.

Then choose how the application reaches you:

  • Client side. The popup hands your page the application and a signed token. Your server must verify the token before it trusts anything in it.
  • Server side. Your webhook hears application.submitted with ids only, and your server reads the application through the API. Redirect mode, for in-app browsers, needs it.

What every recipe shares

  • The popup is certo's own page. Never an iframe: the candidate sees certo's address, signs in there and presses Apply there. Your page never sees the sign-in.
  • The candidate consents to exactly the terms. The consent screen names your organisation, the job, the site's host, what you will read and the checklist. Terms never come from the page: the button's attributes and the popup's address carry the job's words and your state, nothing else, so an edited page or an injected script can never ask a candidate for more.
  • You are the reader. The organisation that owns the button receives the application, always. A job board may name the hiring company (data-hiring-company); the candidate sees it as the site's words, never as a certo organisation, and it reads nothing.
  • It is free. No verification is spent, by you or by the candidate. You read what the passport holds: a verified passport's outcomes, or an unverified one's Claimed lines, and the checklist.
  • The candidate can withdraw. On Access, at any time. You hear application.withdrawn.
  • Each application keeps its terms. terms on an application is a snapshot of what it was made under, with its source. Changing a position or the general terms later changes the next applications only.

The pages of this cookbook

  1. This page.
  2. Before you start: the company profile, the sites, the delivery, the keys.
  3. Recipe a: the general application
  4. Recipe b: apply sessions
  5. Recipe c: a position
  6. Receiving it in the page, and verifying the token, in Node, Python and PHP
  7. Receiving it on your server: the webhook, then the API
  8. Redirect mode
  9. After the application: the later events and a withdrawal
  10. Testing
  11. Errors and troubleshooting