Skip to content

API & integrations

The short answer: for LEO, LEO Fiscaal, ZIA, VERA, BEVER and MAIA the Prudai Developer API is in early access. In production the catalogue, the account, usage, the sources and conversations work today; chat, models and knowledge bases are coming soon. Besides that you connect through the official integrations. For IRMA the API opens up step by step for developers and AI agents. See IRMA for developers. Login, scopes, approvals, errors, the CLI and MCP are all in Prudai for developers.

DoorWhat you do with itStatus
Reporting incidents (/agent/v1)Your monitoring, SIEM or service desk reports incidents into the Incidenten (incidents) register, with a fingerprint against duplicates.Available, with a service token. Quickstart
The task layer (/v1)Read risks, simulations, framework coverage, registers and incidents; start a simulation. Every answer says how complete it is and where the numbers come from.Available, with the token of a signed-in user. Concepts · API reference (Prudai staff only, sign-in required)
The irma CLIThe same from the command line, for scripts and coding agents.Available; npm i -g @prudai/irma. CLI reference
MCPIRMA as tools in AI clients that speak MCP.Coming soon through the MCP gateway. Agents

Every /v1 endpoint is in the IRMA API reference (Prudai staff only, sign-in required), with parameters, fields, error codes and examples. The rest of the IRMA API, such as the routes behind the web app, is internal and is not published.

  • As a lawyer or end user you do not need to do anything here. You work in the web app and the add-ins for Word, Outlook and Excel; everything you need is there.
  • As an admin or IT of an organization with IRMA you can have incidents reported with a service token, and read through /v1. Start with the quickstart.
  • If you want to connect Prudai to your own tooling (a DMS, intake form or e-signing platform, for instance): that is possible, through one of the integrations below or an agreed custom integration. Chatting with the assistants is not possible with a service key yet.

In IRMA, users with management rights create service tokens themselves, under Beheer → Service-tokens (Management → Service tokens). Such a token is a key for your own organization that lets a script or automated job, for example a monitoring tool, submit incidents to IRMA or read them, without signing in.

  • Per token you choose what it may do: incidenten aanleveren (submit incidents) and/or incidenten lezen (read incidents).
  • You see the key once, when you create it. Copy it right away; IRMA only stores a hash of it and cannot show it again later.
  • The list shows each token’s recognizable start (Prefix) and when it was Laatst gebruikt (last used). Intrekken (revoke) disables a token immediately.

Today a service token works for submitting and reading incidents. Scopes for the /v1 task layer are coming. More: IRMA administration and the quickstart.

  • Microsoft SSO + SharePoint for sign-in and documents. See SSO (Microsoft) + SharePoint setup and SharePoint.
  • Word add-in: your assistant inside Microsoft Word, with selection context, insertion and Word-style suggestions. See Prudai For Word.
  • Outlook add-in: save emails and attachments to a dossier, summarize conversations and draft replies. This integration has its own administrator rollout and its own Microsoft Graph permission (delegated Mail.Read, with administrator consent) for full conversations. See Prudai for Outlook and the administrator guide.
  • Excel add-in: the assistant in a task pane plus fixed calculation functions (=PRUDAI.WETTELIJKERENTE, =PRUDAI.CONTANTEWAARDE and relatives) right inside your sheet. See Prudai for Excel.
  • ORDO (on request): ORDO is a separate product for practice management and documents. If your organization has both LEO and ORDO, they work together: a LEO dossier can be linked to an ORDO matter. If you pick such a linked dossier as the destination in the Outlook add-in, emails and attachments end up in ORDO. Documents in an ORDO matter (uploads, archived email, files from SharePoint) are searchable in LEO, in a conversation linked to that matter. See ORDO and ORDO and LEO (sign-in required).
  • Exact Online (MAIA, on request): MAIA answers management questions from your organization’s own Exact Online administration. MAIA only reads and changes nothing in Exact. Prudai sets up the connection and sends an invitation link; someone at your organization with access to the administration uses it to grant permission in Exact Online. See MAIA (sign-in required).
  • Custom integrations (DMS, CRM, forms) are arranged through your account manager and set up and documented per organization.

Want a new integration or to connect existing data? Contact your account manager or reach out via Troubleshooting & support. We will work out which integration fits best and which permissions it needs.

More: Quick start · SSO (Microsoft) + SharePoint setup · Privacy & security.