Skip to main content

Webhooks

A webhook is a way for Oho to tell your other systems the moment something happens — automatically, without anyone logging in to check. You give Oho a web address, choose the events you care about, and Oho sends a message to that address each time one of those events occurs.

Think of it as Oho tapping your HR system, compliance dashboard, or Teams/Slack channel on the shoulder: "this worker's Working With Children Check was just verified," or "this applicant has finished their recruitment check."

When Oho sends one​

Oho can send a webhook when:

  • A credential is verified — checked against the issuing registry, whether it passed, failed, or needs review.
  • A worker or applicant is linked to a credential, or that link changes — for example, when an applicant is hired and becomes a worker.
  • An applicant finishes a recruitment check — every requested credential has a result.
  • A worker finishes a fetch request — they've supplied every credential you asked for.

You choose which of these you want. Oho only sends the events you've subscribed to.

Why use them​

Webhooks keep your other systems current without anyone polling Oho or re-keying data. When a credential's status changes, your compliance dashboard, HR system, or messaging channel can update itself within seconds — no manual export, no scheduled job.

Setting one up​

Connecting a webhook is a developer task. It involves giving Oho an endpoint to call, confirming that each message genuinely came from Oho, and handling the occasional retry. Your engineering team will find the full walkthrough — code samples, the exact payloads, and a recovery runbook — in Webhooks & Event Delivery.

Next​