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.
Google Analytics 4 measures statistically how the website is used. During your visit we also 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.
Google Ads measures which requests reach us from our ads (conversions), without your name, email or phone number. It is not loaded until you accept this category.
Integration · Open
If your system is not on the list, this is for you. REST API v4 reads and writes in attendo, webhooks notify your systems when something changes, and a flow step calls any API without coding.
What it solves
No company lives in a single tool. The ERP wants to know what was done in the field, the website wants to open tickets and the dashboard wants real times. Without an API, someone exports to Excel every Monday.
With the API, each system talks to attendo directly and only about what it needs. You create one key per integration, give it only what it needs, and know who called, for what and when.
What it does
Three pieces that work together: REST API v4, webhooks and the HTTP step in flows.
Documents and their history, customers, contacts and contracts, quotes, orders and delivery notes, assets, projects, flows and checklists. Also requesters, field by field, scheduling, tasks, forms and mailing list sign-ups. Links to files are signed and expire after an hour.
Each key with its name, expiry, owner and rate limit. You pause or revoke one without touching the others.
Each key can only do what you allow, and it is checked on every request. There are starting packages: read-only, field, sales, ERP and AI assistant.
An integration can act on behalf of a user: what it writes is recorded in their name, and it only sees what that person sees on screen.
attendo notifies your systems when a document is created, closed, answered or changes status. Also when an asset is edited, a form is submitted or a customer, contact or contract changes. When a customer is deleted, the notification carries only its identity.
A flow step calls any REST API with the document’s data, and your system starts an attendo flow with one call.
The OpenAPI documentation is interactive: you try the calls from the browser before writing a line of code. And an API activity screen shows requests, webhook deliveries and their errors.
What travels
With the same rules as the screen: a tag brings its checklists along, and a document uses up its series number.
| Data | Direction | When |
|---|---|---|
| Documents, history and attachments | Directionfrom attendo to your system | WhenWhen your system asks for them |
| New documents and changes | Directionfrom your system to attendo | WhenWhen your system sends them. With an idempotency key, a retry does not create another one |
| Customers, contacts and contracts | Directionbetween attendo and your system, both ways | WhenWhen they are requested or sent |
| Assets, plans and projects | Directionbetween attendo and your system, both ways | WhenWhen they are requested or sent |
| Change notifications (webhooks) | Directionfrom attendo to your system | WhenNear real time, with history and retry |
| Flow trigger | Directionfrom your system to attendo | WhenWhen your system calls |
Getting started
It is set up in Settings, with no involvement from us. The integration that uses it is built by your technical team or a partner, and we can support you if you need it.
Status Available
Typical effort. Creating a key takes minutes. The effort is in the integration that uses it: your technical team or a partner builds it.
With the integration’s name, its expiry, just the permissions it needs and an owner. The secret is shown only once.
You authorize the key in the interactive documentation and try the calls before coding.
You choose the events, store the signing secret and send a test to your receiver.
The API activity screen tells you which requests arrived, which deliveries failed and why.
Honesty
Document types, fields and permissions are configured on screen, not through the API.
Through the API, users are listed, activated and deactivated; they are created on screen.
Prices, taxes and numbering come from the same calculations as the screen.
There are events for documents, assets, forms, customers, contacts and contracts. For anything else, your system reads the history through the API.
Your receiver must accept repeated or out-of-order notifications.
Keep going
All integrations Every connection, with its real status.
Frequently asked questions
API v4. It includes everything from the earlier versions, which are retired on March 31, 2027.
Yes. You give the key read access to customers and, if you want to go further, restrict it by operation.
You revoke it in Settings and it stops working instantly. Every other integration keeps working.
120 per minute per key by default, which can be raised per key or for the whole instance.
Each webhook is signed with your secret. Your receiver checks the signature and rejects old notifications.
It is REST with JSON: any HTTP client works.
Request a demo
We will show you what the API would do with your system and which part your technical team would take on.
Would you rather talk first?
