One integration, or one per positionWhere 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_…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_…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_…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()
})