# Connect Kolinea to your tools through the API

> One key per workspace, rights chosen area by area, and documentation generated from the product itself.

## Your folders live elsewhere too

A quote leaves your management software, an appointment your calendar, a client record your CRM. Copying that information by hand into each folder takes time, and that is where mistakes creep in.

Kolinea’s API lets your tools do it for you: open a folder, add a participant, publish a document request, fetch a document you received or update a contact.

## One key, precise rights

1. In your workspace settings, under Developers, you create a key. It starts with `kol_live_` and is shown only once.
2. For each area (folders, participants, thread, requests, comments, documents, contacts, fields, templates, members…), you choose None, Read or Write. A key that only needs to read cannot change anything, and a key that publishes requests is not thereby allowed to answer them.
3. You give the key to the tool that will use it: your business software, an automation tool able to call an API, or your own code.

You can give a key an expiry date, change its rights without changing the key (the tool follows from its next call), and delete it at any time: the tool using it loses access at once. A key also stops working as soon as the member who created it leaves the workspace.

## What a key can do, and what it never will

- A key belongs to one workspace and never leaves it: it sees no folder of another workspace.
- It reads the thread as the team does, internal notes included, but never a confidential publication addressed to someone else.
- The documents it downloads appear in the folder’s access log, under its name.
- What it publishes in a thread carries the name you gave it, marked “Integration”. Your clients know the message comes from an app, not a person.
- It does not delete the workspace, change the plan, create another key or ever give the admin role.

## Told as soon as something moves

Rather than polling the API, your tool can be told. In the workspace settings, you give a webhook address and choose the events to receive: a client answered a request, a document arrived, a folder was closed… Each delivery is signed and carries only identifiers: your tool reads the details back with its key, within its rights.

## Documentation that is always current

The API documentation is generated from the product itself: every endpoint, the rights it requires, the fields it expects and an example answer, with calls ready to copy. It cannot describe an old version of the API. The OpenAPI specification can be downloaded too, to generate a client or import it into Postman.