Skip to content
Start a project

API integration services

Our API integration services connect the systems your business already uses, so data moves between them without copying and pasting: CRM, ERP, payments such as UPI and M-Pesa, WhatsApp and Google Sheets.

Systems that do not talk to each other cost time and cause errors. We connect them through their APIs, test each connection with real records, and add alerts so your team knows when something fails. Where a system has no API for what you need, we tell you and suggest the next-best route.

Start a projectSee an example
APIs and integrations
Illustration of apis and integrations work, with sample content

For example: paid orders from your online store appearing in your accounting system and a Google Sheet, without anyone copying them across.

An illustration of the kind of work we do, not a client project.

After an order is paid today

Before
StoreOrder paid
Accounting systemTyped in by hand
Sales sheetUpdated at the end of the day

Connected

After
Payment receivedUPI
Accounting systemInvoice created
Sales sheetRow added
If a connection failsYour team is alerted

What our integration services include

  • CRM and ERP connections

    Customers, orders and invoices kept in step between your CRM, ERP and accounting system.

  • Payment integrations

    UPI, M-Pesa and regional gateways connected to your store, app or invoicing, with payment status sent back.

  • WhatsApp and Google Sheets

    Order updates and reminders on WhatsApp, and live data in the Google Sheets your team already uses.

  • Custom APIs, with documentation

    An API for your partners or your own apps, documented so another developer can use it.

  • Alerts when a connection fails

    If a connected system is down or rejects a record, your team is told and nothing is silently lost.

  • Tests for each integration

    Each connection is tested with real records, including failures and duplicates.

Want this for your business?

Tell us what you need. A founder reads every enquiry and replies with questions or a proposed scope.

Start a project

Who it’s for

  • Businesses entering the same data twice

    Orders typed into the store, then the accounting system, then a spreadsheet.

  • Teams that want their tools connected

    WhatsApp, payments or a CRM linked to the systems you already rely on.

  • Products that need an API for partners

    Partners and resellers who need to place orders or read data from your system.

What you get at handover

Everything is handed over in your name, so you can run it, change it or move it to another team.

Handover record Checked by a reviewer
  • The integrations, running in your own accounts
  • A diagram of which system sends what, and when
  • API documentation for any custom API
  • The alert settings, and who receives each alert
  • A written manual fallback for each connection
Illustration of a handover record

What we need from you

A project moves fastest when these are ready. We help you put together anything you do not have yet.

  1. 1A list of the systems to connect and what should move between them
  2. 2Admin or API access to each system
  3. 3Sample records for testing: orders, customers or invoices
  4. 4A named person to receive failure alerts

How an engagement runs

  1. Scope document

    Scope: customer portal

    What we deliver

    • Customer sign-in, with roles
    • Order status page
    • Invoice downloads
    Not includedMobile appDone whenTested with your real orders

    Agreed by you before the build starts

  2. This week’s build

    This week’s increment

    Order status page

    Ready to view

    feat: order status page

    test: status for each order type

    docs: how statuses are calculated

    Next increment: invoice downloads

  3. Review checkpoint
    Our reviewer
    • Checked against the scope
    • Tests read and run
    • Ready for you

    Your approval

    Approve milestoneRequest changes
  4. Handover pack

    Code repository

    In your account

    Credentials record

    Transferred to you

    Documentation

    What was built and how

    Runbook

    Deploy, roll back, fix common problems

    Maintenance available on a monthly plan

    Offered as

What affects the cost

We quote after a scoping conversation, so there is no fixed price on the site. These are the factors that move the cost of this work up or down; the proposal states the scope, what is not included and the price.

Technologies we commonly use

  • REST and webhook APIs
  • UPI and regional payment gateways
  • M-Pesa
  • WhatsApp Business messaging
  • Google Sheets
  • Python and TypeScript
Number of systems and directions
A one-way sync between two systems is smaller than a two-way sync across four.
Quality of each system’s API
Well-documented APIs are quicker to connect than older systems without one.
Volume and timing
Real-time updates and high volumes need more careful design than a nightly sync.
Data mapping
How different the systems’ fields are, and how much clean-up the data needs.
Monitoring and alerts
Who is told when something fails, and how.

Questions

The ones your customers use, including UPI in India, M-Pesa in East Africa and regional gateways elsewhere. We confirm the provider’s API during scoping.

Related services

All services

Internal tools

Replace spreadsheets with tools for tracking, reporting and approvals.

AI automation

Workflows between your tools that remove repetitive manual work.

Maintenance and support

Updates, fixes, backups, monitoring and small changes on a monthly plan.

Tell us what you want to build.

Describe the work. We will scope it with you, or tell you plainly if it is not work we should take on.

Start a projectAll services