> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-hris/lucca-integration.md).

# Connect Lucca

Connect Lucca to Siit with your company subdomain and a Lucca API key created by a user with sufficient rights, so Siit syncs your employee data from Lucca

### Connecting to Lucca

💁🏻‍♂️ *Siit will only have access to the same information as the user configuring the connection*\*,\*\* so in order for the integration to work properly make sure that a Lucca user with sufficient rights is configuring the integration.\*

Select **Connect** in the Lucca row to open the configuration dialog.\
​

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-3925f84c602220f1b1bed500d8920e619238208c%2Fcfa2f9ac-image.png?alt=media" alt=""><figcaption></figcaption></figure>

1. Enter your **company subdomain** in the first field.\
   ℹ️ *Your company domain is what is **before** .*[*Lucca.fr*](http://25419906.hs-sites-eu1.com/en/connecting-with-lucca-siit-help-center) *in your Lucca login URL, ex: if your URL is*`https://Siit.lucca.fr` *your company subdomain is* Siit\*.\*\
   ​
2. **Creating a new API key**

   To create a new API key, go to the wheel > Authentication, SSO and API > API Keys. If you don’t have the access rights, please contact Lucca support team.

   ​
3. Please click **Generate API key** to create a key.\
   ​
4. In the creation window, you can
   * Customize the name of the key
   * Select the permissions you wish to associate to this key
5. Once you log in, you'll be automatically redirected back to Siit and the integration will be configured.

Enter your **company subdomain** in the first field.\
ℹ️ *Your company domain is what is **before** .*[*Lucca.fr*](http://25419906.hs-sites-eu1.com/en/connecting-with-lucca-siit-help-center) *in your Lucca login URL, ex: if your URL is*`https://Siit.lucca.fr` *your company subdomain is* Siit\*.\*\
​

**Creating a new API key**

To create a new API key, go to the wheel > Authentication, SSO and API > API Keys. If you don’t have the access rights, please contact Lucca support team.

​

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-41233c55115851045728ca464f336704418feeb6%2Fhrome_wlrta4DtL3.png?alt=media" alt=""><figcaption></figcaption></figure>

Please click **Generate API key** to create a key.\
​

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-d0e408abc486c9f6171f9e2a8efbf8478b990733%2Fgenerercleapi.png?alt=media" alt=""><figcaption></figcaption></figure>

In the creation window, you can

* Customize the name of the key
* Select the permissions you wish to associate to this key

Once you log in, you'll be automatically redirected back to Siit and the integration will be configured.

From now on, Siit will synchronize your employee information from Lucca with Siit including information about employee's **role**, **department**, **office**, and **Start date**...


---

# 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://docs.siit.io/guides/integrations/integrations-hris/lucca-integration.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.
