Apply with certo

One button. A verified application.

A button for your job pages. The candidate signs in to certo in a small window, sees what you will read, and presses Apply. You receive their passport with who confirmed each line, and the checklist you set.

  • Free for you and for the candidate
  • No cookie or tracking on your page
  • The candidate can withdraw at any time

Implement Apply with certo on your page for free.

One script and one button. No fee for you or for the candidate, and no cookie on your page.

How an application works

Four steps, and the candidate never leaves your page.

  1. 01Your page shows the buttonOne script and one button on your job page. It opens certo in a small window over your page.
  2. 02The candidate sees what you will readWho receives it, the job in your words, what you will open, and your checklist with what is ready. Signing in takes a code sent by e-mail.
  3. 03They press ApplyThat gives your company access to their passport. It is free for both of you, and they can add what is missing later.
  4. 04You receive itThe passport with who confirmed each line, the checklist, and anything they verify later. If they withdraw, you read nothing more.
One integration, or one per position

Where the terms of an application come from.

What you read and what you ask the candidate to have ready are the application's terms. The id on the button decides where they come from, never the page, so nobody can edit them in a browser.

ao_…

A single integration

One id for every job. Your general settings decide what you read; the button names the job in your words, so each application says what it was for.

Best for: a careers site with many jobs and one way of hiring.

<script async
  src="https://certo.bio/apply/v1.js">
</script>
<button
  data-certo-apply="ao_..."
  data-job-ref="DA-114"
  data-job-title="Data analyst">
</button>
ap_…

Using a position's data

A position that takes applications has its own id. Its checklist and what it reads become the terms, and every application lands under that position in Candidates.

Best for: a role that asks for more or less than the rest, such as a right to work in one country.

<button
  data-certo-apply="ap_...">
</button>
as_…

A session from your server

Your server opens a short-lived apply session through the API with the terms for this job, then the button opens it. Nothing about the terms is in your page at all.

Best for: job boards and ATS systems that set terms per job or per company.

// your server, at api.certo.bio
POST /v1/apply-sessions
{ "job": { "ref": "DA-114" } }
-> { "apply_session":
     { "id": "as_..." } }

// your page
CertoApply.open({
  session: () => yourServer()
})
Client side or webhook

In your page, or on your server.

The same application reaches you one of two ways, switched on in your Apply with certo settings. You can use both.

In your page (client side)

  1. 1The candidate presses Apply in the window.
  2. 2The window hands your page the application and a token certo signed, and only at your page's address.
  3. 3Your page sends it to your server, which checks the token against certo's published keys.
Best when
you run the careers site and want the application at once, with no API key.
What to trust
the signed token only, checked on your server; never the page's copy alone.
button.addEventListener('certo:applied', (e) => {
  // the application and its signed token
  fetch('/api/certo', { method: 'POST',
    body: JSON.stringify(e.detail) })
})

On your server (webhook)

  1. 1The candidate presses Apply in the window.
  2. 2certo sends application.submitted to your webhook, signed with your secret. It carries ids, never the passport.
  3. 3Your server reads the application through the API, a read the candidate can see.
Best when
an ATS or a job board takes it from there, or the page that shows the button is not yours.
What to trust
the webhook's signature, then the API's answer.
// your webhook receives
{ "type": "application.submitted",
  "data": { "application": { "id": "..." } } }

GET https://api.certo.bio/v1/applications/{id}

There is also a plain link for e-mails and a mode that returns to your address instead of a window. The integration guide has both, with tested code.

What keeps it honest

Safe for the candidate, and for you.

Only where it should run
The button works at once on your company's checked domains. Any other site that shows it is reviewed by a person at certo first.
Signed, not trusted
Each application in the page comes with a token certo signed. Your server checks it against certo's published keys before it believes anything.
The candidate decides
They see who receives it and exactly what you will open before they press Apply, and they can withdraw it later.
Every read is logged
Each time your company opens the passport, the candidate sees it under Who opened it.

Let candidates apply with a verified passport.

Free for your company and for every candidate. Set it up in your console under Integrations.