Recruiting & ATS · Integration
Referoo
Add Referoo to your product for your customers, and give your AI agents governed access to it.
Referoo runs employment reference checks, background checks and identity verification, and its OAuth 2.0 API exists precisely so a check can be raised from the system a recruiter already works in rather than from Referoo's own screens. The objects are candidates, the requests raised against them, the referees a candidate named, the questionnaire each referee answers and the completed report. Consent is what makes this different from a normal record read: a referee is a third party who agreed to be contacted about someone else, so who was asked, what they were asked and when they replied all have to be recorded rather than inferred. Referoo already sits behind ATS platforms, so your product is usually one more place the same request originates. fastn owns the auth and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Referoo account so checks are raised under their brand and their questionnaires.
Create a request for a candidate and follow it through to a completed report without anyone leaving your product.
Read referee responses per tenant so a hiring decision rests on the recorded answer rather than a forwarded email.
Map each customer's own questionnaires, since what a referee is asked differs by role and by country.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which reference requests are outstanding and how long each has been waiting.
An agent raises a request within scoped permissions, and the candidate and referee it touched are logged.
An agent summarises a completed report for a hiring manager, citing the responses it read.
Example prompt
Which reference checks are still incomplete for this candidate, and which referees have not responded yet?
Set up Referoo in 4 steps
- 01Enable the Referoo connector in your fastn dashboard.
- 02Have each customer authorise their own Referoo account so requests are raised under their credentials.
- 03Map the candidate fields, questionnaires and request statuses your product uses, then enable the triggers you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Referoo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Referoo integration without building it. Your customers connect their own Referoo account inside your product and work their job requisitions, candidates and applications there, with no per-customer code on your side.
- Handle the part that actually costs time: candidate records are personal data with consent and retention rules attached. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Referoo update is not your on-call problem.
- One integration serves your product and your agents. The same governed Referoo connection powers in-product features and gives AI agents scoped, audited access, so you keep hiring pipelines moving without manual re-entry without wiring it twice.
Used by these teams
Compare with
JobAdder
Greenhouse
CheckrOften used alongside
Tools the same teams tend to run next to Referoo, across other categories.
Slack
Notion
Box
DocusignReferoo integration FAQ
How do I add a Referoo integration to my product?
Enable the Referoo connector in your fastn dashboard, then let each customer authenticate their own Referoo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Referoo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Referoo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Referoo account and only ever sees their own job requisitions, candidates and applications. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Referoo integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which reference requests are outstanding and how long each has been waiting.
Who maintains the Referoo integration?
fastn does. When Referoo changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How is candidate data from Referoo handled?
Access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged. That matters more here than in most systems, because candidate records are personal data that carry consent and retention obligations.
Can my product react when a candidate's status changes in Referoo?
Yes, through event triggers: a stage move where Referoo owns the pipeline, or a completed assessment, a returned report or a finished reference where it owns one step in it. Events are delivered per tenant and can be replayed after an outage, so a hiring team does not silently lose an update while your product was unreachable.
What can I build with the Referoo integration?
A common starting point: let each customer connect their own Referoo account so checks are raised under their brand and their questionnaires. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Referoo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Referoo does not change your per-connector cost. You can start free with 3 connected accounts.
Add Referoo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.