API interfaces that finally get your systems talking to each other.
MacNorris, based in Hamburg, builds API interfaces between CRM, ERP, shop and accounting, including for systems without an API of their own. Your data moves between your tools automatically instead of via CSV export and manual import. If someone on your team moves files from one system to another every morning, you're in the right place.
CSV export, manual import, errors, repeat.
Every morning someone exports a file from system A and imports it into system B. Maybe it even runs automatically, with a script from 2018 that nobody wants to touch. Sometimes it works, sometimes it doesn't. And when it doesn't, someone notices three days later.
Almost all cloud and SaaS tools have open APIs today. Through an API, systems talk to each other in real time, reliably and without manual steps. Even phone and WhatsApp can be connected this way, for example with Twilio Voice.
What CSV files and night scripts used to handle is now done by a properly built interface. It is faster and more stable, and nobody has to check first thing Monday whether the import ran.
What is an API interface?
An API interface is an agreed way for two programs to exchange data. One system requests data or reports a change, the other responds or takes it on. Nobody moves files in between anymore.
Two kinds matter to you. With a request, a system fetches data when it needs it, for example prices from the ERP. With a webhook, a system reports on its own that something has changed, for example a new order in the shop. Which standard sits behind it, REST, GraphQL or SOAP, we work out per system.
And if a system has no API out of the box, we build the access ourselves. For almost every database there are connectors that let us get the data out cleanly.
Three forms of interfaces we implement every day.
Which form fits depends on how many systems are involved and whether they already have an API.
Direct system-to-system interfaces
CRM talks to ERP. Shop system talks to inventory. Accounting gets data straight from the source. Without manual work and without copy-paste errors.
Your data is current in every system.
Middleware APIs
In larger environments a central middleware pays off. Instead of addressing each service individually, it coordinates the requests. One system asks once, several respond in the background, and the logic lives in one place.
That means fewer dependencies and easier maintenance.
APIs for systems without an API
Not every system comes with an open interface. For legacy systems, older databases or proprietary software we build connectors that enable data access from the outside.
That way no system stays an island.
How we build your interface.
Map data flows
Which data lives where, who needs it and how often? The result is an overview your team understands too.
Clarify access
We check which systems have an API and which access the vendor grants. Where no API exists, we plan a connector.
Build and test
First with test data, then with a small share of real data. The full volume runs only once everything checks out.
Monitor operations
Every data transfer is logged. If a transfer fails, you know right away, not three days later.
Clean interfaces are not an IT task. They are the foundation for everything that comes after.
Automations need reliable data. AI projects need clean data foundations. Reporting needs a single source of truth. All of that only works when the systems in the background talk to each other reliably.
We work with API interfaces every day, regardless of which systems, regardless of which industry. We develop custom interfaces, build middleware solutions and make sure data arrives where it is needed, without workarounds and without anyone having to check the import first thing Monday morning. For workflows we often use n8n. What it costs to run is in our n8n cost comparison.
Three systems. One truth. No more manual exports.
A company runs a shop system, an ERP and a CRM. Customer data is manually synchronised between all three systems, daily, by one person who spends two hours on it. Errors happen regularly.
We build a middleware that connects all three systems. Customer data is automatically synchronised whenever a change occurs in any of the systems.
- Daily manual effort reduced from 2 hours to 0
- Data errors from duplicate maintenance eliminated
- New customer in shop: immediately available in CRM and ERP
- Changes in ERP: immediately visible in all systems
- Middleware documents every data transfer, full traceability
Typical challenges regarding API interfaces
API Development for Systems Without an API
API development for systems without an interface: why missing APIs are not a dead end, how to build them and what that means for your data.
CSV Export Automation: Without Manual Work
CSV export: why export, edit and import is not a process, what goes wrong with encodings and delimiters, and how APIs solve this for good.
Data Silos: When Every System Has Its Own Truth.
Breaking down data silos: why marketing, sales and accounting all have different numbers, and what missing interfaces have to do with it.
ERP Integration Without a Big IT Project
Why the 'too risky' argument in ERP interfaces is usually wrong, which data should actually flow, and what a clean CRM-ERP integration delivers.
WhatsApp Business With Multiple Users
WhatsApp Business is built for one phone, not a team. How several users reply together, via app, Slack or MS Teams, without a base fee per user.
What you usually ask us about API interfaces.
In most cases, yes. We work with the existing interfaces and databases and don't touch the core system. Your ERP or CRM keeps running as before. If access is missing, we talk to the vendor or your IT partner and work out the best route together.
Then we build the access ourselves. For almost every database there are connectors that let us read and write data without rebuilding the system. With older software, export functions or a small dedicated service that provides the data often do the job. More on systems without an interface.
We build it so you understand it yourselves afterwards: with documentation, a clear structure and no vendor lock-in. We don't build in dependencies on us that aren't necessary. The knowledge stays in your company, and your team can maintain and extend the interface on its own.
A direct connection between two systems that already have APIs is often up and running after one day. A middleware for several systems needs more preparation, because we clarify data flows and edge cases first. That too is done within a few days. Tell us briefly about your systems and we'll give you a firm timeframe.
It depends on a few drivers: how many systems are involved, whether they already have an API, how much data flows and whether it has to arrive in real time. A simple connection costs far less than a middleware. So we talk briefly about your project first, then estimate the effort and tell you the price.
An ERP interface connects your ERP to other systems such as your shop, CRM or accounting. Orders, customer data, prices and stock levels then flow back and forth automatically instead of via export. Many ERP systems come with an API, older ones often don't. Either way, we build the connection so your ERP stays the leading system.
Your systems don't talk to each other. We change that.
Tell us briefly which systems need to be connected. We'll tell you in one conversation what is possible.