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

Testing Apply with certo

Run the whole flow on localhost with your own passport, send a webhook test, try sessions as a dry run, and check the list before you go live.

2 minute read

You can run every recipe end to end before a single candidate sees the button, against your own data and nobody else's.

On localhost, with your own passport

A page on http://localhost or http://127.0.0.1, any port, can open the popup without review, listed under Where it runs or not, with one rule: only a member of your company can apply from it, with their own passport. Anybody else gets apply.test_origin_members_only. So sign in to the popup as yourself.

On a live site the rule turns round: a member of your company cannot apply to it (apply.own_organisation). Test on localhost, or with a colleague who is not a member.

Your test applications are real applications: they appear on Hiring and in the numbers. Withdraw them on your own Access page when you are done.

The webhook

Press Send a test event on the Webhooks page, or call POST /v1/webhook/test: one webhook.test event, signed like every other, tried once. Your signature check must accept it. Then apply from localhost and watch application.submitted arrive.

A local endpoint is not reachable from certo: the webhook must be https on a public host name. Use a tunnel to your machine, or a staging host of your own.

Apply sessions as a dry run

POST /v1/apply-sessions?dry_run=true runs every check and answers the terms the candidate would see, without making a session (recipe b). Use it to build your terms before you open a popup.

Verifying the token

The samples answer the first failed check by name. While you build, log that name: nonce means the state you kept is not the one on the button, aud that you compared with another id, exp that more than ten minutes passed, replay that the token was used before.

Before you go live

  • The company profile is complete and Apply with certo is switched on.
  • Every site the button runs on is Live, not waiting for certo. Remove the localhost sites you no longer need.
  • The general application is saved, or every button opens a position or a session.
  • The page sends the token to your server, and your server verifies it; nothing trusts the page's JSON.
  • Your state is fresh per visitor and kept on your server.
  • The webhook answers 2xx within ten seconds and handles an event once, by certo-event-id.
  • Your key has only the scopes it needs, and lives on your server.
  • A withdrawal deletes what the application opened.