> For the complete documentation index, see [llms.txt](https://help.join.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.join.com/integrations-and-api/external-hr-tools/d.vinci.md).

# d.vinci

The d.vinci integration allows JOIN to automatically forward all incoming applications to your d.vinci applicant tracking system (ATS). Job postings are imported into JOIN using your d.vinci XML feed, and applications collected via JOIN are delivered directly into d.vinci, streamlining your recruitment pipeline.

{% hint style="warning" %}
Before you begin, make sure to review the [External HR tools](https://help.join.com/integrations-and-api/external-hr-tools.md) article to understand the general requirements and limitations that apply to all integrations (e.g. sync frequency, job limits, multi-language/locations, screening questions).
{% endhint %}

Once connected, the d.vinci integration allows you to:

* Import published jobs from d.vinci into JOIN using your XML feed
* Automatically forward candidate applications from JOIN into d.vinci every 30 minutes
* Continue managing your job content fully within d.vinci

***

### Connect d.vinci and JOIN

Contact our [Support team](mailto:contact@join.com) to activate the integration. Include the following details:

* **XML Feed**\
  This is the URL of your d.vinci job feed\
  Format: `https://<your-subdomain>.dvinci.de/en/jobs`\
  → Your subdomain is the same as the one used for your d.vinci-hosted career page
* **Login**\
  The integration-specific username provided by d.vinci
* **Password**\
  The integration-specific password provided by d.vinci

Our team will review your request and notify you once the integration is active.

***

### **Limitations**

* **Job sync direction**\
  JOIN cannot push jobs into d.vinci. All job data is imported from your XML feed. To make any edits or archive a job, you must do so in d.vinci.
* **Screening questions**\
  JOIN’s screening question functionality is not supported in this integration.
* **Job filtering**\
  JOIN imports all jobs from your XML feed. If your feed contains more jobs than your JOIN plan allows, a random subset will be published. Filtering is not available.

***

### FAQs

<details>

<summary>How does JOIN get jobs from d.vinci?</summary>

JOIN reads your job postings from your d.vinci XML feed. These jobs are then published via JOIN automatically. Jobs successfully synced are marked with a green checkmark <i class="fa-circle-check">:circle-check:</i> and labeled `Synced` in within JOIN.

</details>

<details>

<summary>How does job sync between d.vinci and JOIN work?</summary>

JOIN imports your job postings directly from the d.vinci XML feed. To ensure jobs publish correctly, your feed must include all standard fields:

* Job title
* Job description
* Location
* Employment type
* Language and posting settings

Once imported, JOIN will automatically publish these jobs on your JOIN page and distribute them to standard job boards.

{% hint style="warning" %}
JOIN does not create, edit, or archive jobs inside d.vinci. We only display what’s present in your feed.
{% endhint %}

</details>

<details>

<summary>Can JOIN update or archive jobs in d.vinci?</summary>

No. JOIN cannot modify or archive jobs within d.vinci. You must manage all job content directly in d.vinci.

</details>

<details>

<summary>Where do candidate applications go?</summary>

All applications collected via JOIN are forwarded to d.vinci every 30 minutes, including additional candidate data if supported.

</details>

<details>

<summary>Are screening questions supported?</summary>

No. Screening questions are not supported in the d.vinci integration.

</details>

<details>

<summary>What should I do before activating the integration?</summary>

To avoid duplicate postings, archive any manually created jobs in JOIN before enabling the integration.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.join.com/integrations-and-api/external-hr-tools/d.vinci.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
