Software Development
API & Systems Integration
Connect ERP, CRM and third-party systems
Every growing company ends up with systems that do not talk to each other: an accounting package, a CRM, an ERP, a store, a warehouse system, a payment gateway, and a few spreadsheets holding the whole thing together. The cost shows up as people re-typing data, numbers that disagree between reports, and decisions delayed while somebody reconciles two versions of the truth.
Integration work makes data move once, in one direction, with a record of what happened. It is unglamorous and it is exactly the kind of work that quietly removes a full-time job's worth of manual effort.
What's included
What we integrate
ERP systems
orders, inventory, purchasing, financials and master data.
CRM platforms
leads, contacts, pipeline and activity, kept in step with your website and product.
Accounting and invoicing
invoices, credit notes, payments and reconciliation, posted automatically instead of keyed in.
Payment gateways
cards, wallets, instalments and bank transfer, including the refund and settlement paths people forget to plan for.
Logistics and courier services
rates, labels, pickups and tracking updates pushed back to the customer.
Government and regulatory portals
where an official integration route exists for submissions and validation.
HR, payroll and identity systems
staff records, single sign-on and access provisioning.
Marketing and communication tools
email platforms, SMS and messaging providers, and analytics destinations.
Selected clients in Software Development
8 clients
Building an API of your own
Sometimes the answer is not connecting to somebody else's system but exposing your own, so partners, apps and internal tools can all use one interface instead of three private arrangements. We design and build those properly:
- REST or GraphQL, chosen for the consumer rather than by preference, and documented as it is written.
- Authentication and authorisation with scoped keys or tokens, so a partner sees only their own data.
- Rate limiting, pagination, filtering and idempotent writes — so a retried request does not create a second order.
- Versioning from day one, because the second consumer arrives sooner than expected and cannot be broken by your next change.
- Webhooks with signature verification and a retry policy, for the partners who need to be told rather than to poll.
- A sandbox environment and readable documentation, which is what actually determines whether anyone integrates with you.
Integrations fail on the bad days, not the good ones
Anyone can move a record between two systems when both are healthy. The engineering is in what happens when they are not, and this is where most integration projects turn into recurring manual work:
- Retries with backoff, so a five-minute outage does not need a person to re-run anything.
- Idempotency, so a repeated message does not duplicate an invoice.
- A dead-letter queue for records that cannot be processed, with a screen where someone can see and fix them.
- Reconciliation jobs that compare both systems and report drift, because silent divergence is worse than a visible failure.
- Monitoring and alerting that tells you a sync has stopped, rather than you finding out from a customer.
- Audit logs of every message sent and received, which is what makes disputes resolvable.
Where there is no API
Plenty of important systems have no usable API — an on-premise ERP, a legacy database, a supplier who sends a spreadsheet by email. There are still dependable routes: scheduled file exchange with validation, direct database replication into a reporting store, or a small adapter service that presents a clean interface over an old one. What we avoid is fragile screen-scraping presented as an integration, and we will say so rather than build something that breaks the first time a vendor changes a page.
On working with Codigoo
The first thing they did was tell us to stop two campaigns we were proud of. That is when I knew they were reading the numbers and not the brief.
Questions we are usually asked
- Can you work with our existing vendor's system?
Usually, and it does not require their cooperation to begin — but if they hold the credentials or control the interface, involving them early is faster than working around them. We can run that conversation on your behalf, in technical terms they cannot deflect.
- Should data sync in real time?
Rarely does everything need to. Real-time matters for stock levels and payments; a nightly batch is fine for accounting exports and reporting. Real-time everywhere multiplies cost and failure modes, so we choose per data flow and tell you the trade-off.
- Who owns the integration afterwards?
You do — the code, the credentials and the documentation. If you want us to keep watching it, that goes into a support agreement with a defined response time, because an unmonitored integration is a liability rather than an asset.
- What about data protection?
Integrations move personal data, so what is transferred, where it is stored and who can read it are decisions to make deliberately. We map the data flows in writing, keep transfers encrypted, restrict credential scope to the minimum, and avoid copying personal data into systems that have no reason to hold it.
If two of your systems disagree about the same number, that is the symptom worth bringing to a consultation.
More in Software Development
All of this discipline- Web Application DevelopmentScalable web platforms and customer portals
- Mobile App DevelopmentNative and cross-platform iOS and Android
- E-Commerce DevelopmentOnline stores built to convert and scale
- Custom Software & Internal ToolsAdmin dashboards and operations tooling
- AI & AutomationIntelligent workflows and predictive models
- Cloud & DevOpsCI/CD, infrastructure and cloud migration
Talk to us about API & Systems Integration
Thirty minutes with an engineer and a strategist who do this work — not a sales team. You will get an honest answer about whether it is the right thing to buy, and what it would realistically cost.