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: Plus and Premium — not included on Core
What you get
- Ask for exactly the credentials you're missing, with guiding text against each one
- Ask a worker to confirm or update their address, personal phone or personal email — with or without credentials
- 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 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 moves through Sent and Opened to Submitted and Completed as they respond, and they can reopen the link to correct anything until it expires (14 days by default).
→ 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.
Good to know
- The worker needs an email address on file. Oho sends to their work email, or their personal email when there's no work one. A worker with neither still gets a request created, but nothing is ever sent — see Before you start.
- A fetch request goes to an existing worker. To screen someone before they start, send a recruitment check instead — see Recruitment check requests.
- Requests are visible to everyone assigned to the worker's organisation, not just whoever sent them — see Who sees which 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.
- A request can collect contact details instead of credentials. A details-only request completes as soon as the worker submits — see Confirm or update contact details.
- Oho can send renewal requests for you. With Send workers a renewal link on, a worker gets a fetch request when a credential starts expiring, tagged Renewal in the list. It doesn't check for one you've already sent, so a worker can end up with two — see Requests Oho sends for you.
- 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.
- Workers with an Australian mobile can be texted the link as well as emailed it — see Customise SMS 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
requirementsblock instead, for AND/OR groups, exemptions, or ban checks — see the Fetch Requests tutorial.