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

Recipe c: a position

Switch "Accept applications with certo" on a position, in the console or with the API, and paste its button. The position's terms are the application's.

2 minute read

When your jobs live in certo as positions, each position can take applications itself. The position holds the terms (what candidates are asked for), counts its applications, and stops them when it is closed.

1. Switch it on

In the console. On Hiring, pick the position in the column and press Take applications. Owners, admins and recruiters can. The position's id for the button, ap_ and 32 hex characters, and its snippet appear in the dialog.

With the API. PATCH /v1/positions/{id} with the key's hiring:write scope (Change a position, in the API reference); POST /v1/positions takes it too:

curl -X PATCH https://api.certo.bio/v1/positions/0192f1c4-7a10-7c2e-9d41-3b8e2f0a5c11 \
  -H "Authorization: Bearer $CERTO_API_KEY" \
  -H "content-type: application/json" \
  -d '{"accepts_applications": true}'

The answer's position carries accepts_applications and apply_id, the ap_ id. Only an open position can be switched on (apply.position_closed otherwise).

2. Paste its button

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

<button data-certo-apply="ap_5f0c2a9e1b7d4c3a8e6f1d2b9a7c4e10"
        data-job-ref="REQ-2026-114"
        data-state="st-9d1e5c7a2b"></button>

The position's title is the job's title the candidate sees; data-job-ref is still kept on the application, so your own reference comes back. Every other attribute, the JavaScript form and the events are as in recipe a.

Where no script runs (an e-mail, a PDF advert, a social post), link to the popup itself: https://certo.bio/apply/<the ap_ id>. It opens with no page behind it, so nothing is posted back to a page: the candidate applies, sees that it was sent, and you hear application.submitted on your server and read the application through the API, as in server side. Integrations, Apply with certo shows each position's link beside its button.

What the position decides

  • The terms. The position's What candidates are asked for is exactly what the application opens. Changing the position later changes the next applications only; each application keeps a snapshot of its terms (terms.source is position).
  • Where it is filed. Each application sits under the position on Hiring, with the source chip Applied, beside the invited candidates.
  • When it stops. Closing the position, or switching Accept applications off, makes its button open on apply.position_closed; nothing is written. The ap_ id is kept, so switching on again revives the same button.

Different terms for one candidate

To ask one candidate for more, or to keep the job's words on your server, make an apply session that names the position: the position's terms are its defaults, anything you give replaces them, and the application is filed under the position.