Skip to content

API integration services

We connect the systems your business already runs on, such as your CRM, payment provider, booking tool, accounting software and couriers, so data moves between them on its own instead of being copied by hand. A single integration is a fixed price from £3,500 and takes 2 to 4 weeks; a platform that joins several systems starts at £12,000.

We reply within one working day. 020 7078 5151

Problems you shouldn't have to live with

  • The same data typed in twice

    Orders land in one system, invoices are raised in another and the customer record lives in a third. Someone on your team spends part of every day moving it between them, and the gaps show up as missed invoices and wrong addresses.

  • An integration that quietly stopped

    A Zapier flow or a script a past developer wrote has been failing for weeks and nobody noticed until a customer asked where their order was. Nothing told you, because nothing was watching.

  • A system with no obvious way in

    The supplier's API documentation is thin, needs an OAuth app that has to be approved, or has rate limits that a naive sync hits in the first hour. You can't tell whether the job is two days or two months.

  • Quotes with no fixed number

    Everyone says "it depends" and offers a day rate. You want to know what connecting two named systems will cost, how long it takes, and what happens when one of those systems changes its API next year.

How we solve it

  1. 1

    Payments and billing

    Stripe and GoCardless: checkout and subscription events delivered by webhook into your own records, failed payments and refunds handled, and every event processed once even when the provider retries. Our own site takes Stripe payments this way.

  2. 2

    Accounting

    Xero and QuickBooks: invoices, payments and contacts created from your orders or bookings, reconciled against what the accounting system already holds, and tax codes mapped once so your bookkeeper stops correcting them.

  3. 3

    CRMs and marketing

    HubSpot and Salesforce: leads, deals and lifecycle changes kept in step with your website, app or order system, in both directions where it matters, with field mapping agreed in writing before anything is written.

  4. 4

    E-commerce, bookings and shipping

    Shopify and WooCommerce orders, stock and customers synced with your warehouse, booking platform or courier accounts (Royal Mail, DPD, Evri and others with an API), including labels, tracking numbers and the status updates customers actually read.

  5. 5

    Open Banking and public data

    Account information and payment initiation through a UK Open Banking provider, and lookups against Companies House, Royal Mail's Postcode Address File or HMRC where your workflow needs them, with the consent and audit records those sources require.

  6. 6

    App stores and your own apps

    App Store Connect and Google Play Developer APIs for listings, sales reports and review handling, and the API behind your own app or portal. We publish our own App Store listings and translations through the App Store Connect API.

Technologies we use

Node.js TypeScript Next.js Google Cloud Run PostgreSQL Firestore BigQuery OpenAPI OAuth 2.0 Webhooks Stripe Xero HubSpot Shopify

How it works

How an integration project runs, and what it costs

The same four stages on every integration, a fixed price for the scope we agree, and a straight answer on whether you need custom code at all.

  1. 1

    Discovery: which systems, which direction, which records

    A short call and a written brief: the systems involved, what should move between them, in which direction, how often, and what "correct" looks like for a record that exists in both. We check access to each API (keys, OAuth apps, sandbox accounts, approval queues) before we quote, because that is where the surprises live.

    You get a one-page scope with a fixed price and a start date, usually within two working days of the call.

  2. 2

    Mapping: fields, edge cases and the rules in writing

    Every field that moves is written down with its source, destination and any transformation (a Shopify order line to a Xero invoice line, a HubSpot deal stage to a status in your app). We agree what happens to duplicates, partial records, refunds, cancellations and time zones before the first line of code, and the mapping document becomes part of the handover.

  3. 3

    Build: retries, idempotency and monitoring from day one

    Integrations fail in boring ways: a timeout, a rate limit, a provider retrying the same webhook three times. We build for that from the start. Every incoming event carries an idempotency key so it is processed once; every outgoing call retries with backoff and respects the other side's rate limits; every failure is logged with enough detail to replay it; and an alert reaches you (and us, on a plan) when something stops.

    The code lives in your repository from the first week, with a staging environment pointed at the providers' sandboxes so you can test with real-looking data before anything touches a live account.

  4. 4

    Handover: your code, your accounts, your documentation

    You own the code and every account it uses. The handover includes the mapping document, a runbook for the failures we expect (expired token, changed API version, a provider outage) and a walkthrough with whoever will look after it. Most clients then put it on our Ongoing development plan, but you can take it to any developer.

  5. 5

    What it costs

    A single integration between two systems, one or two directions, is a fixed price from £3,500 and takes 2 to 4 weeks. That covers discovery, the mapping document, the build with retries, idempotency and monitoring, a staging environment, tests and handover. Most single integrations land between £3,500 and £6,000; a two-way sync with history to backfill is usually £6,000 to £8,000.

    An integration platform or middleware layer, where three or more systems share one set of records and rules, starts at £12,000 and takes 6 to 10 weeks. Typical platforms land between £12,000 and £30,000. You pay a 50% deposit to book the start date and the balance on launch. No VAT is added. Subscriptions to the systems themselves, and any provider's API fees, are yours.

  6. 6

    API integration platform or custom code: which one you need

    An integration platform (an iPaaS such as Zapier, Make or n8n) is the right answer more often than agencies like to admit. If you need to move a lead from a form to a CRM, post an order to a spreadsheet or send a Slack message when a payment lands, one of those tools will do it for a few pounds a month and you don't need us. We will tell you that on the call, and we are happy to set the flows up as part of a wider project.

    Custom code wins when the data matters enough to need guarantees: payments and invoices that must never be duplicated, syncs that have to recover from a failure without re-running everything, volumes that make per-task pricing expensive, records that live in both systems and change in both, a system with no connector, or anything that needs an audit trail. Our rule of thumb: if a wrong or missing record costs you money or a customer, build it; if it costs you a minute, use the tool.

After launch

Keep it working after launch

Websites and apps need looking after once they're live. Ongoing development is the plan most people choose after this, at from £1,500 a month.

Already have an app or site that needs looking after?

Questions we get asked

A single integration between two systems is a fixed price from £3,500, with most landing between £3,500 and £6,000 depending on how many records move, in how many directions, and how much history needs backfilling. A middleware layer joining three or more systems starts at £12,000, with typical platforms between £12,000 and £30,000. You get a fixed price for an agreed scope before we start, and anything outside that scope is quoted separately before any work is done.

Ready to talk about your project?

Let's talk about your project and the best way to approach it. No commitment and no pressure, just a conversation about what's possible.