Solutions / API integrations
API integrations
Two systems that do not talk today
I leave an integration between two systems you already use, documented, so a change does not vanish in silence.
What this is
An integration, in this package, connects two systems that do not talk today. It includes authentication, retries and a place to see if something failed, so a change does not vanish in silence. More than two systems, building the system that does not exist yet, and third-party API costs sit outside. The result is a technical note for keeping it, not a black box.
Experience
At Zenta I turned business requirements into REST and SOAP integrations and data flows on mixed architectures, legacy and cloud. At Falabella the purchase journey depended on that: payment gateway, order release and dispatch. The package is deliberately two ends. If a third system appears, or one that still has to be invented, it is written down before we start.
How I work
I use two ways of ordering the work. They are not creeds. Each one fits a different moment.
Waterfall
First we write the whole path and what sits outside it. Then we build in that order. It fits when the scope can already be named: a six-screen site, an integration between two systems, an Odoo start with three modules. You know what you will receive before we begin.
Scrum
The work is split into short weeks. Each week something usable is shown, and we decide what comes next. It fits when the detail is still being found: an agent's tone, the question that actually reaches the bot, the priority in a backlog.
The published package is the frame: scope, timing, and what is quoted separately. That is waterfall. Inside it there is a weekly review: we look, we correct, we carry on. That is Scrum. I hold a Scrum Master certificate and Scrum Foundations, plus a Green Belt for when the problem is operational rather than fashionable.
Who it is for
Anyone who already has a CRM, an ERP, a shop or an internal tool and needs the data to travel on its own.
What the package includes
- An integration between two services
- Authentication and error handling
- Retries and a log of what goes in and out
- A test of the happy path and of one failure
- A technical note for keeping it
Quoted separately
- More than two systems in the same package
- Building the system that does not exist yet
- Third-party API costs