The Kolinea API: your tools work in your folders
What you do from the API
Open a folder, add a participant to it and publish a request or a document request in it
Fetch a document you received, read the thread as the team does, update a contact
Duplicate a folder for the next year or the next session
Download an approval’s certificate, or a closed folder’s closing register, as a PDF
Record an approval given elsewhere, naming the participant and how the answer came in
Say a request is being handled, with an expected date, and answer an extension request
Connecting the API, step by step
In your workspace settings, under Developers, create a key: it starts with kol_live_ and is shown only once.
For each area (folders, participants, thread, requests, documents, contacts…), choose None, Read or Write.
Give the key to the tool that will use it: it sends it in the Authorization: Bearer header of every call.
Your folders live in your other tools 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. It answers in JSON, every call carries the workspace’s key, and the key only gets the rights you gave it, area by area. A key that only needs to read cannot change anything, and a key that publishes requests is not thereby allowed to answer them.
A key you keep in hand
The key is shown only once, when it is created; Kolinea keeps only its fingerprint. You can give it an expiry date, change its rights without changing the key (the tool follows from its next call), and delete it at any time.
The documents it downloads appear in the folder’s access log, under its name. What it publishes carries the “Integration” mark: your clients know the message comes from an application, not a person.
What the API can do with a folder
Beyond opening and publishing, a few endpoints serve to keep the proof or to chain one folder onto the next. A folder can be duplicated for the following year, with the participants you keep and its fields, filled in or empty; no one is notified. An approval’s certificate can be downloaded from the first answer, and a closed folder’s closing register as a PDF: the Verify a document page recognises both.
Documentation generated by the product
The API documentation is produced from Kolinea’s code: it cannot describe an old version of the API. Every endpoint is listed with the rights it requires and a sample answer, with calls ready to copy.
To be told about a change rather than polling the API, connect webhooks. The endpoints specific to folders are detailed on the API and integrations page.
What the integration does not do
A key belongs to one workspace and never leaves it: it sees no folder of another workspace.
It never reads a confidential publication addressed to someone else.
It does not delete the workspace, change the plan, create another key or ever grant the administrator role.
It never gives an approval on someone’s behalf: it only records one a participant gave elsewhere.
Beyond 120 calls per minute for one workspace, the API answers 429, with the Retry-After header.
The features involved
Your questions before connecting
Another question? Contact us
It is generated from the product itself: every endpoint, the rights it requires, the fields it expects and a sample answer. The OpenAPI 3.1 specification can be downloaded at /v1/openapi.json, to generate a client or import it into Postman.
Yes. What a key publishes in a thread carries the name you gave it, marked “Integration”.
A POST carrying the Idempotency-Key header runs only once: for 24 hours, a new attempt with the same body gets the answer already given.
Delete its key: the tool loses access at once. A key also stops working as soon as the member who created it leaves the workspace.
Other integrations
Your next folder, with nothing lost along the way
Not the right time?
Get the link by e-mail and pick up later, from your computer.
One e-mail only, and your address is not kept.