Recruiting & ATS · Integration
d.vinci
Add d.vinci to your product for your customers, and give your AI agents governed access to it.
Embed a d.vinci integration so your customers can work their own job postings, applications, candidates, and hiring stages from inside your product, with governed agent access to the same records. Applicant data is sensitive, so access is scoped per tenant, limited to the fields you map, and every read and write is logged. fastn handles each customer's authorisation and API upkeep, so onboarding another instance is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own open job postings into your product so vacancies appear where candidates already are.
Create an application from your product so a candidate does not have to re-enter their details.
Read candidate records and hiring stages so recruiters see progress without switching tools.
Trigger your product when an application arrives or a candidate changes stage.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a candidate's application and current stage before drafting a reply.
An agent updates a candidate record or logs a note within governed permissions.
An agent reacts to a new application and runs the first screening step.
Example prompt
List applications received in the last week that nobody has reviewed yet, grouped by job posting.
Set up d.vinci in 4 steps
- 01Open the d.vinci connector from your fastn dashboard.
- 02Have each customer authenticate their own d.vinci instance.
- 03Map the job posting, application, and candidate fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the d.vinci integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a d.vinci integration without building it. Your customers connect their own d.vinci 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 d.vinci update is not your on-call problem.
- One integration serves your product and your agents. The same governed d.vinci 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
Ashby
CATSWorks well with
BambooHROften used alongside
Tools the same teams tend to run next to d.vinci, across other categories.
Slack
Notion
Box
Docusignd.vinci integration FAQ
How do I add a d.vinci integration to my product?
Enable the d.vinci connector in your fastn dashboard, then let each customer authenticate their own d.vinci account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no d.vinci client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own d.vinci account?
Yes. Every connection is scoped to the individual customer, so each authorises their own d.vinci 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 d.vinci 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 reads a candidate's application and current stage before drafting a reply.
Who maintains the d.vinci integration?
fastn does. When d.vinci 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 d.vinci 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 d.vinci?
Yes, through event triggers: a stage move where d.vinci 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 d.vinci integration?
A common starting point: read their own open job postings into your product so vacancies appear where candidates already are. 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 d.vinci integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding d.vinci does not change your per-connector cost. You can start free with 3 connected accounts.
Add d.vinci to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.