Skip to content

API and webhooks

Updated:

API keys with validity and IP list, webhooks and the BI feed under Settings → Integrations & API.

Open Settings in Fiatto
In this article

Alongside SSO/SCIM and the accounting integration, Fiatto offers a REST API, webhooks and a BI feed. Admins manage them under Settings → Integrations & API (/dashboard/settings/integraties).

Steps

  1. Open Settings (account menu) → Integrations & API.
  2. Create a key in API keys: enter a name, choose the Validity (30, 90 or 180 days or 1 year) and optionally fill in Allowed IP addresses (one address or CIDR range per line). Click Create key and copy the key right away: you only see it once. In the sandbox the key carries _test_ in its name and only works on the practice environment.
  3. Keep rights narrow. An API key (scope api) works on /api/v1: read and write purchase requests, purchase invoices, contracts, suppliers and programmes; read and create customers and sales orders; read and submit legal tickets; read-only for sales invoices and sales contracts, purchase orders, goods receipts and payments. A sales order created through the API arrives as a draft, with the same checks as on screen (such as the credit limit) and a mandatory Idempotency-Key. The fixed handovers between modules are available as a feed on /api/v1/handovers. The general ledger (journal entries and trial balance) and the audit trail for a SIEM are switched on separately per key; only an approver or accountant can issue ledger access. A key from BI connector (Power BI / Excel) has scope bi.read and only works on the read-only OData feed.
  4. Add an endpoint under Webhooks, choose the events and send a test event; failed deliveries appear in the delivery log. Rotate secret creates a new signing secret; the old one stays valid for 24 hours. Per endpoint you choose the Message format: Fiatto (default) or CloudEvents 1.0 (the open standard; a handover then arrives exactly as in the feed). The event list also includes handovers (handover.*) and the contract lifecycle, such as contract.created, contract.status_changed, contract.renewed and contract.expired.

Tips

  • Never use API keys in a browser or mobile app. Keys cannot be extended: create a new key, put it in your integration and revoke the old one. Admins and the creator get a reminder 14 and 3 days ahead; a key unused for 90 days is revoked automatically after a warning. An IP list can only be narrowed afterwards (Narrow IP list). For every API, BI and assistant key you see when and from which address it was last used; if it has no IP list yet, Restrict to this address limits it to that address in one click.
  • Each key has a default limit of 120 requests per minute; read the X-RateLimit-* headers to slow down before a 429. The versioning policy is in /api/v1/openapi.json and in the Deprecation/Sunset headers: a version is announced at least 12 months in advance.
  • A SIEM can subscribe a webhook endpoint to the event for security events (sign-ins, two-step verification, role and policy changes, emergency button, support access).
  • In the sandbox every webhook endpoint is a test endpoint: each delivery carries the header X-Fiatto-Environment: test (live in your real environment), and API keys and test webhooks remain when you reset the sandbox. See practice in the sandbox.
  • All integrations with their status, third-party apps and the developer portal are under Settings → Integrations & apps (marketplace) (/dashboard/settings/koppelingen). Connecting Claude or ChatGPT: outside AI assistants. Taking data along without the API: data export.
Was this article helpful?
View all articles in this topic

Find another answer

A task, feature or short question is enough.