API v4, REST and documented
Documents, customers and contacts, assets, projects with their line items, checklists and attachments. The OpenAPI schema is browsable and lets you try the calls before writing any code.
Choose which cookies you accept. You can change this at any time from “Cookie settings” in the footer of every page. Cookie policy
They make the website work, remember this choice, keep your conversation with the assistant if you use it, and protect the forms from bots. They cannot be turned off.
During your visit we remember the campaign source you arrived with and the page you landed on, so we know which campaigns and pages bring us requests. Cloudflare Web Analytics counts visits without cookies and does not depend on this option.
Used to measure our campaigns on Google Ads, LinkedIn and Meta. None is active on the website today.
API v4, webhooks and MCP
API v4, two-way webhooks, and MCP as both server and client. Each key performs only the operations you allow: if it leaks, the possible damage is what you decided.
Data and integrations
Documents, customers and contacts, assets, projects with their line items, checklists and attachments. The OpenAPI schema is browsable and lets you try the calls before writing any code.
One key per integration, with permissions by area and by operation. Operations are grouped in bundles: read-only, field, sales, ERP and AI assistant. Expiry, rate limits and revocation.
Your integrations sign in with system accounts, which do not use a license. Each one has only the permissions it needs, and the allowlist is checked on every request.
Outgoing, to notify your systems when something happens, with history and resend. Incoming, so an external system can trigger a flow. And a flow step calls any API without code.
Connect your assistant, such as Claude or ChatGPT, and ask about documents, customers or assets. It answers with what that person is allowed to see and cites where it got it. Writes come turned off.
attendo also connects to third-party MCP servers. From a flow or from the record, an agent asks your ERP whether a part is in stock. The answer goes into their reply.
How it works
This is how it is used day to day, on the same document as the rest of the modules.
With the operation bundle the integration needs, its expiry and its limit.
With the OpenAPI schema and a staging instance, before touching real data.
Via API, via webhook or with a flow step that calls their API.
Every outgoing webhook keeps its history, and it can be resent if needed.
With the MCP server, your AI assistant queries attendo with each person’s permissions. And as an MCP client, marIA asks your ERP or other MCP servers from the record. Every marIA operation is logged with who ran it, the model and its cost.
Where it is used
Industry solutions
Honesty
Instance configuration is not done via API: document types, fields, permissions and flows are configured in the interface.
There is no published rate limit, but there is abuse control. If you plan to move a lot of volume, we size it with you.
Works with
Odoo, SAP Business One, Business Central and Holded, connected
See ERP integrationFlows, phased processes with approvals, and AI inside the flow
See Flows and AI-FlowsSELECT supplier, COUNT(*) … GROUP BY supplier Ask in plain language. Get answers from your data, with the source.
See AI-Chat and DB AssistantGlossary
Processes and automation
HTTP callback · reverse API
A webhook is an automatic notice that one system sends to another, at a web address, as soon as something happens: a new order, a payment or an approved document.
Maintenance
PdM
Predictive maintenance decides when to intervene based on the real condition of the equipment, measured through vibration, temperature, power draw or oil analysis, not by calendar.
Maintenance
Critical spare
A critical spare part is one whose absence holds up the repair and drags out the equipment’s downtime. It is not the most expensive part or the most used one: it is the one you cannot get quickly.
Frequently asked questions
Yes. API v4 has a browsable OpenAPI schema where you can try the calls.
It can only perform the operations on its allowlist, and you revoke it without touching the others. The possible damage is what you decided when you created it.
The server lets your assistant query attendo. The client does the opposite: attendo connects to third-party MCP servers and queries them from a flow or from the record.
Not by default. Writes come turned off, and turning them on requires a double lock.
Yes. We set up a staging instance so you can test your integration.
Request a demo
We will show it to you with your own document types and the way you work. If it is not a fit, we will tell you.
Would you rather talk first?