We have recently released our new Webhooks API, which deserves a blogpost, both because we want to share new additions, but also in particular to share some details about how it functions.

This release introduces two new endpoints:

• Webhooks
• EventTypes

These endpoints make it possible to manage webhook subscriptions programmatically and fetch which events are available for subscription, it requires the superuser role in order to access the webhooks API.

You can explore the documentation here:

• The full documentation
• Webhooks API documentation
• EventTypes API documentation

Webhooks allow you to receive information from e-conomic. Instead of polling the API repeatedly to detect changes, your integration can subscribe to events and receive notifications automatically whenever something happens in an agreement.

Typical use cases include synchronizing customers, invoices, or products. Triggering workflows when bookkeeping events occur or keeping external systems updated automatically and reducing scheduled synchronization jobs.

We’ve supported webhooks for a while, but until now managing them required manual setup through the GUI. With these new APIs, webhook management no longer requires the individual user to access the GUI which was necessary prior.

Important behavior to be aware of

There is one important detail regarding visibility of webhooks:

The API will only return webhooks that were created by the same App. For example, if any user within an agreement creates a webhook manually in the UI, another integration user querying the API will not receive that same webhook in the response.

• Webhooks created through the e-conomic UI will not be returned
• Webhooks created by another user will not be returned
• Only API-created webhooks belonging to the authenticated API user are visible through the endpoint

This decision was made intentionally to ensure that applications cannot interfere with each other’s webhook configurations where integrations are present.