API and Integrations
A public REST API with tokens and granular permissions so your website, your online shop or any other application can talk to the system.
No company keeps everything in one program, and it does not need to. What it does need is for data not to be copied from one screen to another by hand, because that is where errors appear and where the time nobody counts gets lost.
Each integration authenticates with its token and can do exactly what it is authorised to do and nothing else, which lets you give a third party access without opening up the whole system. The usage log shows which integration is calling, how often and with what result, which is what lets you diagnose things when something stops working.
The usual cases are concrete: the website form creating a lead in the CRM, the online shop syncing orders and stock, the plant machine reporting output, or head office tooling that needs to read each branch's sales.
What it is used for
What still lives outside the system
No company keeps everything in one program, and it does not need to. What it does need is for data not to be copied from one screen to another by hand, because that is where errors appear and where the time nobody counts gets lost.
The cases the API solves are concrete and recur in almost every rollout:
- Your website form creating the opportunity in the CRM with its source tagged.
- The online shop syncing orders, stock and customers.
- A plant machine reporting output or readings.
- Head office tooling that needs to read each branch's sales.
It is documented for developers, so whoever connects it does not depend on somebody explaining each field by email.
Permissions per integration
Granting access without opening the whole system
This is the part that decides whether an integration is acceptable or not. Each integration authenticates with its own token, and that token can do exactly what it is authorised to do and nothing else.
That lets you give access to a third party, a website or a service provider knowing they can only touch what applies to them: creating leads, reading stock or checking orders, without reaching invoicing or personnel data.
And when the relationship with that third party ends, you revoke the token and that is it, with no need to review which users were created or which passwords are still circulating.
When something breaks
The usage log is what makes diagnosis possible
Integrations stop working for mundane reasons: a credential expires, a field changes, a server stops responding. The failure is not the serious part; discovering it weeks later because leads stopped arriving and nobody noticed is.
The log shows which integration is calling, how often and with what result. When something fails, the question of whether the problem is on your side or theirs is answered by looking, rather than by two technical teams blaming each other over email.
It works the other way too: seeing that an integration has not called for a month usually means the other side changed something and did not mention it.
Clearing things up
Frequently asked questions
Answers to what we get asked most.
What is the API normally used for?
For your website form creating the lead in the CRM, the online shop syncing orders and stock, a plant machine reporting output, or head office tooling that needs to read each branch's sales.
Can I limit what each integration does?
Yes. Each authenticates with its own token and can do exactly what it is authorised to do and nothing else, so you can give a third party access to create leads or read stock without them reaching invoicing or personnel data.
What happens when a provider relationship ends?
You revoke their token and that is it, with no need to review which users were created or which passwords are still circulating.
How do I know if an integration has stopped working?
Through the usage log, which shows which integration is calling, how often and with what result. Seeing that it has not called for a month usually means the other side changed something without saying so, and without that log you find out through the leads that stopped arriving.
Reporting, dashboards and integrations
Reports you build yourself without writing SQL, dashboards per user and an API so your systems talk to each other.
BI · Custom Reports
Build your own reports over the system's real data with a visual editor: pick the dataset, drag in the columns, apply filters and get tables, indicators and charts, without writing a line of SQL.
View moduleCustom Dashboard
Each user or department builds their own dashboard with a widget assistant (sales, treasury, services, HR, stock) and finds it waiting when they log in.
View moduleCentre Reports
Scheduled reports generated and emailed at whatever frequency you set.