Skip to content
decidio — Digital citizen participation

Integrations

How external systems connect to decidio through the public interface and the webhook system.

Overview

A municipality rarely runs only one system. decidio therefore offers two paths for connecting to third-party software: a public interface for read and write access and a webhook system that forwards events to external systems.

This page describes the possibilities at a concept level. A detailed reference with all endpoints, data formats and security details follows in a later section — see What comes next.

How it works

The public interface enables read and — depending on permissions — write access to citizen submissions and selected master data. Each municipality manages its own API keys and can issue and revoke them as needed.

The webhook system informs external systems as soon as an event happens in decidio — for example the status change of a citizen submission. The recipients are managed per municipality; retries on transmission errors and a protection mechanism for message authenticity are built in.

Both paths are designed so a municipality's specialist software — such as the existing council information system or the complaint management — can pick up submissions and keep status changes in sync.

Common tasks

Generate an API key

  1. In the settings open the "Integrations" area.
  2. Create a new key and give it a clear name.
  3. Hand the key to the authorised place — it is shown only once and can then be used in the intended place.

Configure a webhook target

  1. In the "Integrations" area create a new webhook target.
  2. Pick the events to be transmitted.
  3. Prepare the receiver address and the signature settings for the third-party system — details follow in the reference.

Review an existing connection

In the "Integrations" overview check the status of keys and webhooks. Delivery errors are flagged so the affected third-party system can be addressed directly.

Related topics

What comes next

The detailed developer reference is now available as API reference and Webhook reference. The API reference covers endpoints, authentication, pagination, rate limiting, and errors. The webhook reference covers event types, payload, signature verification, and the delivery contract.