Skip to main content

Developers

Pour :Administrateur
Open in Unisoft

The Developers module lets you connect Unisoft to your external tools: no-code automations (Make, n8n, Zapier), in-house scripts, external CRMs, etc. It gathers two integration mechanisms: API keys and outgoing webhooks.

Two complementary building blocks​

Unisoft integrations rely on two different mechanisms, which answer two distinct needs. You can use them independently or in combination.

API Keys — to fetch data​

An API key lets an external tool query Unisoft on demand to retrieve information: the contact list, the week's payments, a form's submissions, etc.

Use case examples:

  • A Make scenario that synchronizes new contacts to Mailchimp every hour.
  • A Python script that exports payments to an accounting tool every night.
  • An external dashboard (Looker, Metabase) that queries the API to display KPIs.

In plain terms: it is you (or your tool) who asks Unisoft for data when you need it.

Outgoing webhooks — to be notified in real time​

An outgoing webhook is the opposite: it is Unisoft that calls your tool as soon as a business event occurs (a new payment, a submitted form, a created contact…).

Use case examples:

  • Automatically send a personalized thank-you email to each new donor (via Make).
  • Create a Trello card as soon as a "request a meeting" form is submitted.
  • Notify a Slack channel for every donation above €500.
  • Synchronize new contacts to your main CRM (HubSpot, Salesforce) in real time.

In plain terms: it is Unisoft that notifies you as soon as something happens, without waiting for you to ask.

Interactive API documentation​

At the top right of the Developers page, a "API Documentation" button opens the interactive Swagger documentation of Unisoft. There you find:

  • the complete list of available endpoints;
  • the request format (parameters, body, headers);
  • the response format (with JSON examples);
  • the ability to try the calls directly from the browser (after authentication with your API key).

This is the reference resource for your developers or to configure an HTTP call in Make / n8n / Zapier.

The two tabs​

The /app/developpeurs/tabs page is organized into two tabs:

Security best practices​

Integrations give external tools access to your data in Unisoft. A few golden rules:

RuleWhy
One key per useIf a key is compromised, you revoke it without breaking other integrations
Minimum permissionsLimit each key to strictly necessary permissions (e.g., only paiements:read)
Store secrets in a vaultNever in clear in an unprotected file; use a password manager or environment variables of your tool
Revoke when in doubtA revoked key immediately stops the integration; better recreate it than leave an active risk
Monitor last useA key never used for several months is suspicious; revoke it

Takeaways​

  • The Developers page is accessible via direct URL: /app/developpeurs/tabs.
  • Two mechanisms: API keys (you query Unisoft) and outgoing webhooks (Unisoft notifies you).
  • The API Documentation button opens the interactive Swagger to explore endpoints.
  • On the security side, one key per use and minimum permissions are the two essential rules.

Go further​