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

Apply with certo: before you start

What has to be in place first. A complete company profile, the sites the button runs on, how applications reach you, the webhook and the API key.

3 minute read

Everything on this page is done once, by an owner or an admin of your company, under Integrations, Apply with certo in the console. Recruiters see the page and the numbers, and switch positions on, but do not change these settings.

Your company profile

Apply with certo is for employers, and it switches on only once the company profile is complete: the logo, the name, the country, the website and a description (Completing your company profile). The consent screen shows the candidate your name and logo, and your verified mark only where certo verified your company.

Switch it on

The switch at the top of the page turns the whole integration on and off. Off, every button of yours opens on apply.paused and nothing is written. certo may also pause a company's integration; the page then says so with certo's note.

Where it runs

The popup runs only when the page that opened it is on one of your sites. Under Where it runs, add each one as a Site (origin): https://, the host name and, if there is one, the port. No path, no wildcard, no IP address. For example https://careers.acme-robotics.example or https://jobs.hireline.example.

The siteIts status
On one of your company's checked domains (the domains certo checked for you, not only the website on your profile)Live at once
Anywhere else, such as a job board's hostWaiting for certo: certo checks the site is yours, then allows or declines it with a note
http://localhost or http://127.0.0.1, any portAlways open, for testing, even unlisted: only a member of your company can apply there, with their own passport

At most 50 sites and return addresses together. Removing one stops it at once; applications already made stay, because the access is the candidate's to end.

For redirect mode, add each Return address (redirect) too: https on a host name (or http on localhost), with a path and a query if you like, no fragment. It is matched exactly, character for character.

How applications reach you

Choose one or both:

  • To the page (client side): the popup hands your page the application and a signed token, and your server verifies the token (client side).
  • To your server (server side): the webhook event application.submitted, then a read through the API (server side). Set up the webhook first on the Webhooks page (Webhooks for employers). Redirect mode needs this.

Saving neither answers apply.delivery_required.

The general application

Recipe a, and the fallback of recipe b, read the general application: what an application that names no position asks for (the scopes, contact, the date of birth with its reason, the checklist), the same choices a position offers. Until it is saved, a button with an ao_ id answers apply.general_terms_missing. You may use only positions and never save it.

An API key

The buttons of recipes a and c need no key. Recipe b, reading applications on your server and switching positions with the API do. An owner or an admin makes one on API keys (API keys) with the scopes it needs:

ScopeFor
hiring:invitePOST /v1/apply-sessions, recipe b
candidates:readGET /v1/applications/{id}, the application with the passport (each read is logged)
hiring:readGET /v1/applications, the list; with candidates:read, the checklist on an application
hiring:writePATCH /v1/positions/{id} with accepts_applications, recipe c
webhooks:managesetting up and testing the webhook from your code

Keep the key on your server. A request from a browser is refused.

The script

One script tag on every page with a button:

<script src="https://certo.bio/apply/v1.js" async></script>

The path carries its version, v1. Load it from certo.bio as it is; do not copy it to your own host.