Contract first
An agreed schema — OpenAPI or GraphQL — before implementation, so the client and server teams can build in parallel.
Service 06 — API & integration
We integrate your data and resources into your private and public sites and applications — designing APIs worth consuming, and connecting the systems your team already depends on.
Feature work is predictable. Integration work is where estimates die — because the other system's documentation is out of date, its rate limits are undocumented, and its idea of a customer record does not match yours.
We treat every integration as its own small project with its own risk. Before we quote it we read the API, make real calls against a sandbox, and find out where the surprises are. That is why our integration estimates hold when other people's do not.
If you are publishing the API rather than consuming it, the audience is developers and the product is the contract. Versioning, pagination, error shapes, idempotency and rate limits are the interface. We design those first, document them properly, and treat a breaking change as the serious event it is.
Deliverables
An agreed schema — OpenAPI or GraphQL — before implementation, so the client and server teams can build in parallel.
API keys, OAuth or signed requests, scoped to least privilege and rotatable without downtime.
Retries with backoff, idempotency keys, circuit breakers and dead-letter queues, because the other system will go down.
Verified signatures, replay protection and a delivery log, so nobody has to ask whether an event arrived.
Reconciling two systems that disagree about what a customer is, with the conflicts surfaced rather than silently resolved.
Per-integration dashboards and alerts, so a partner's outage is visible to you before it is visible to your customers.
Shapes of the work
| Integration type | Common examples | The usual trap |
|---|---|---|
| Payments | Stripe, PayPal, ACH providers | Webhook ordering and duplicate events |
| ERP / accounting | NetSuite, SAP, QuickBooks, Xero | Rate limits and nightly batch windows |
| CRM & marketing | Salesforce, HubSpot, Klaviyo | Field mapping drift after somebody edits a form |
| Logistics | Carriers, 3PL, warehouse systems | Address normalisation and partial shipments |
| Internal legacy | A twenty-year-old database or a fixed-width file | No sandbox, no documentation, one person who remembers |
Stack
We work in your stack when you have one. These are our defaults when the choice is ours.
Questions
Related
Consumer oriented, enterprise oriented, vertical or horizontal — it does not matter. We build desktop-class software…
Integrate code into a shared repository and verify every integration through automated tests. Then ship it the same…
Get a high-profit e-commerce website that brings in revenue like clockwork. B2B and B2C, on the platform that fits…
Ignition
Tell us the problem, the users and the systems already in place. We will identify the right discovery or build step.