Skip to main content

Fetch requests

Ask an existing worker for a credential detail you don't hold — they fill it in on a secure link, and it lands on their profile, verified where possible.

Who it's for: Compliance admins chasing renewals and missing details

Availability: Available

What you get​

  • Ask for exactly the credentials you're missing, with guiding text against each one
  • Let the worker respond on any device, with no Oho login to create
  • Track each request in one list, from sent through to completed
  • Chase several workers at once from the Requires Attention queue
  • Feed what they submit into the same verify-and-monitor loop as every other credential

Turn it on​

→ Send a fetch request — pick the worker, tick the credentials you're asking for, and Oho emails them a secure upload link.

How it works​

The worker receives an email at their work address with a secure upload link — no login required — and what they submit flows straight onto their worker profile. From there it's treated like any other credential: Oho verifies it against the official source where one exists and keeps monitoring it from then on. The request shows as Awaiting response in the list until they complete it.

→ Fetch credentials from workers — where this sits in the end-to-end journey → Credentials — what happens to a credential once it arrives → Workers — the profile it lands on

For developers

Create a request with POST /fetch-requests, track it through lifecycle.status, and remind, resend, or cancel it. Subscribe to fetchRequest.completed to know when a worker has supplied everything you asked for.

→ Fetch Requests tutorial → Webhooks & event delivery

Good to know​

  • A fetch request goes to an existing worker. To screen someone before they start, send a recruitment check instead — see Recruitment check requests.
  • The credential list starts with what Oho already holds for that worker, which is what you want when chasing a renewal. + Add another credential type covers anything new, including custom credentials an admin has defined.
  • Reminders are largely automatic: a request left unanswered past the reminder window is chased, up to a cap. Resend when the link has expired or you need an email to go out now.
  • From the Compliance Overview you can select several workers in the Requires Attention queue and request info from all of them in one go.
  • The wording and branding of the email is yours to change — see Customise email templates.
  • In the app a fetch request takes a plain list of credential types. Role-based bundles are what screening packages are for, and they apply to pre-hire screening. Over the API you can send a structured requirements block instead, for AND/OR groups, exemptions, or ban checks — see the Fetch Requests tutorial.