A product by

Files extension

The management system archives in Files on its own

Invoices come out of the management system and must land in the client’s folder; surveys arrive from the instrument on site; the client portal must show their documents. With the external API a program talks to Files as a person would: upload, read, share, with an API key instead of a login.

Request a demo Files overview

The same rules, without an interface

Files is already an API: the web interface, the desktop app and the other ecosystem applications all talk to the same REST service. The extension opens that door to a third-party integration with a company API key, issued and revoked by the administrator. What the key can do is what permissions allow: folders, access levels, protections, vault apply to a program as to a person, and every action lands in the audit log with its signature. No shortcuts: an integration does not see a confidential folder and does not open a vaulted file.

How it works

  1. Issue a key

    The administrator creates the key for the integration — “Invoice system” — and decides which permissions it works with.

  2. The program calls Files

    Upload a file to a folder, read it, create a link for it, update a field: the same operations as the interface, over HTTP.

  3. Check and revoke

    Every call is in the log with the key that made it. A compromised key is revoked in one click and the integration stops.

A program is a user with a key. The rules are the same.

What you can do

  • REST, like everything else

    The same API used by the interface and the desktop app: no separate “for externals” subset to maintain.

  • Real permissions

    The key has the permissions you give it. Confidential folders, vault, read-only, retention apply to it too.

  • Signed audit

    “Uploaded by Invoice system” is a log row like any other: whoever checks knows what the program did.

  • Immediate revocation

    A key is switched off from administration and from then on gets in no more. Without changing anyone’s password.

Frequently asked questions

What can I do via the API?

What the interface does: folders and files, uploads and versions, shares, labels and fields, search. For a specific case — a webhook, a high volume — let us talk at activation.

Do I need a dedicated user?

The key represents the integration, with the permissions the administrator assigns it. One key per integration is advisable, so the log says which program did what.

And for folder synchronisation?

To keep a local folder in sync with Files there is Kamzan Desktop, which uses the same API with a ready-made client. The external API is for when the program is yours.

The other Files features

Move your company files to the cloud

Request a demo: we’ll show you how Files makes storage and sharing simple and secure.

Request a demo