Recruiting & ATS · Integration
Xobin
Add Xobin to your product for your customers, and give your AI agents governed access to it.
Xobin is pre-hire assessment with a hiring pipeline attached. A recruiter picks from a large library of skill and psychometric tests, invites a candidate, and gets back a score together with the proctoring signals from that session: screen recording, tab switching, whether more than one face appeared. An embedded Xobin integration creates a candidate and sends an assessment invitation from your own workflow, reads results and their section level breakdown when they land, and receives events when someone completes a test or moves through the hiring stages. The score is the sensitive part, not merely the personal data around it. An assessment result influences whether somebody gets hired, so it should be read from the source with the read logged rather than copied into a spreadsheet nobody can audit afterwards. fastn keeps each customer's credentials per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Xobin account so assessments run under their subscription and their chosen test library.
Invite a candidate to an assessment from your product at the point the workflow calls for one.
Read scores and section level breakdowns so a hiring decision is made where the rest of the evidence already sits.
React when a candidate completes an assessment or a proctoring signal is raised, without anybody watching a dashboard.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises how a candidate scored by section and what the proctoring signals showed.
An agent sends an assessment invitation within scoped permissions, with the test it chose recorded.
An agent lists candidates whose assessments are still outstanding after an agreed number of days.
Example prompt
How did this candidate score by section in Xobin, and were there any proctoring signals worth reading?
Set up Xobin in 4 steps
- 01Enable the Xobin connector in your fastn dashboard.
- 02Have each customer authorise their own account so assessments are drawn from their library and billed to them.
- 03Map the assessments, score fields and proctoring signals your product uses, then enable the completion trigger.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Xobin integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Xobin integration without building it. Your customers connect their own Xobin 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 Xobin update is not your on-call problem.
- One integration serves your product and your agents. The same governed Xobin 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
Codility
Greenhouse
WorkableOften used alongside
Tools the same teams tend to run next to Xobin, across other categories.
Slack
Notion
Box
DocusignXobin integration FAQ
How do I add a Xobin integration to my product?
Enable the Xobin connector in your fastn dashboard, then let each customer authenticate their own Xobin account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Xobin client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Xobin account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Xobin 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 Xobin 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 summarises how a candidate scored by section and what the proctoring signals showed.
Who maintains the Xobin integration?
fastn does. When Xobin 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 Xobin 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 Xobin?
Yes, through event triggers: a stage move where Xobin 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 Xobin integration?
A common starting point: let each customer connect their own Xobin account so assessments run under their subscription and their chosen test library. 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 Xobin integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Xobin does not change your per-connector cost. You can start free with 3 connected accounts.
Add Xobin to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.