APIs and integrations explained: how your business tools can talk to each other

In this article14 sections

1. What are API integrations, in plain English?
2. Why API integrations matter for Nigerian businesses
3. Real examples of integrations that pay for themselves
4. The APIs Nigerian businesses use most often
5. The four ways to connect your business tools
6. How to read API documentation without being a developer
7. How much do API integrations cost in Nigeria?
8. Security: keeping keys, customer data and money safe
9. When integrations break: NEPA, timeouts and duplicate payments
10. A step by step plan for your first integration
11. Five integration mistakes I see again and again
12. Key takeaways
13. Frequently asked questions
14. Next step: connect your first two tools

Funke sells skincare products from a small studio in Yaba, Lagos. Orders arrive from her website, from Instagram DMs and from WhatsApp. Customers pay by Paystack, by bank transfer and sometimes on delivery. Her stock lives in an Excel sheet, her customers live in her phone contacts, and her delivery riders get instructions in a WhatsApp group. Every evening, she and her younger sister sit for three hours copying orders from one place to another: from the website to the sheet, from the sheet to the rider’s message, from the bank app to the “paid” column. Last December they sold the same lip balm to two different people because the sheet was two hours late.

Funke did not need new software. She needed her existing tools to talk to each other, and that is what API integrations do. An API integration is a safe, official connection that lets one program send information to another automatically, so that nobody has to retype it. When it is done well, a payment on Paystack marks the order as paid, reduces the stock, sends a receipt on WhatsApp and tells the rider where to go, all within seconds and without a human touching it.

I am Dan Audu, a software engineer in Abuja. For eight years I have connected shops, schools, clinics and logistics firms to payment gateways, WhatsApp, SMS, maps, accounting tools and their own systems. In this guide I explain API integrations in plain English, with examples from Nigerian businesses, real naira costs as at 2026, the four ways to connect your tools, how to keep them secure, and how to plan your first one. Every technical word is explained in brackets the first time it appears.

What are API integrations, in plain English?

API stands for application programming interface. That is a heavy name for a simple idea: it is the official way that one piece of software asks another for something, or tells it something. An integration is what you get when two systems use their APIs to work together.

The waiter analogy

Imagine you are eating at a restaurant in Wuse 2. You do not walk into the kitchen and cook. You also do not shout at the chef. You tell the waiter what you want, the waiter carries the order to the kitchen in the correct format, and later returns with your food. The waiter is the API. The menu is the list of things you are allowed to ask for, and the kitchen is the system that does the work. You never see the kitchen, and you do not need to.

When your website asks Paystack, “Was this customer’s payment successful?”, it talks to a Paystack API. When your delivery app asks Google Maps, “How far is Garki from Kubwa?”, it talks to the Google Maps API. Each answer comes back in a short, structured message.

A few words you will hear, explained

• Endpoint: a specific address you can send a request to, like one counter at a bank that handles only one job, such as “create payment” or “check balance”.
• JSON: the plain, tidy text format most APIs use to send information, for example a customer’s name, amount and status in labelled boxes.
• API key: a secret code that proves the request comes from you. Treat it like a password.
• Sandbox or test mode: a practice version of the service where you can try things with fake money and fake data.
• Rate limit: a cap on how many requests you can send per minute, so nobody overloads the service.

Webhooks: the doorbell, not the constant peeking

There are two ways to find out that something happened. One is to keep checking: “Has the payment arrived yet? Has it arrived now?” This is called polling, and it wastes effort. The other is a webhook, where the other system rings your doorbell the moment something happens. Paystack, Flutterwave, Monnify and most payment providers use webhooks to tell your website that a payment was successful. It is faster, cheaper and how professional systems are built.

What a real request looks like

To make this less abstract, here is what happens when a customer clicks “Pay now” on a website. Your server sends a request to the payment provider. It contains the amount, the customer’s email address and a unique reference number, such as ORDER-10453. Many payment APIs expect the amount in the smallest unit of money, which for naira means kobo, so ₦8,500 is sent as 850000. The provider replies with a link to a secure payment page. The customer pays there, and a moment later the provider sends a webhook to your server saying “reference ORDER-10453 was paid”. Your server checks the message and updates the order. That is the whole story, and everything else is detail.

Why API integrations matter for Nigerian businesses

You might think this is for big tech companies. In my experience, small businesses gain the most, because their staff time is so limited and they run on so many different tools.

Your business already runs on many tools

Count the tools you use in one day: WhatsApp for orders, your bank app or Moniepoint for money, Paystack or Flutterwave for online payments, Instagram for marketing, a POS at the till, Excel for stock, Google Maps for riders, and maybe Zoho or QuickBooks for accounts. None of these were built to work with your particular business. If they do not share information, you become the connector, and you are an expensive and tired connector.

Double entry costs real money

Suppose two staff members spend two hours each day re-entering orders. That is about 40 hours a month. At an average salary of ₦120,000 a month for such staff, the time costs you about ₦60,000 to ₦70,000 every month, plus mistakes, and plus the quiet fraud that hides in the gaps between systems. A cashier who enters “₦8,500” on the till but “₦5,800” in the sheet is easy to miss when nobody compares the two. Integration removes both the cost and the opportunity.

Speed wins customers

A buyer who pays at 9 pm expects confirmation now, not tomorrow. When your systems talk automatically, the receipt arrives on WhatsApp within seconds, the stock updates before the next person orders the same item, and the rider is told immediately. In a market where a customer can move to another Instagram vendor in a minute, that speed is a real advantage.

APIs protect you from lock-in

There is another benefit that owners rarely think about. When your tools connect through open, documented APIs, you can replace one of them without rebuilding everything. If your payment provider raises its fees, or your POS vendor closes, you swap that piece and keep the rest. Businesses that rely on hidden, one-off connections often find themselves trapped, because nobody remembers how the pieces fit. Good integrations are a form of insurance.

Growth without hiring more typists

Every new branch or channel adds copying work. Without integration, growth means more staff doing boring tasks. With integration, the same team handles three times the volume, because the machines handle the handoffs and the humans handle the customers.

Real examples of integrations that pay for themselves

Here are the integrations I set up most often. Notice that each one connects two things you already own.

Payment, order, receipt and stock

A customer pays through Paystack on your website. A webhook tells your system the payment succeeded. Your system marks the order as paid, reduces the stock, creates an invoice and sends a receipt by email and WhatsApp. If the payment fails or is repeated, the system knows. For online stores, this single integration replaces a large amount of manual checking. I write about the choice of gateway in my Paystack versus Flutterwave guide.

Website, CRM and WhatsApp

A visitor fills a form on your site or clicks a WhatsApp button. Their details go straight into your CRM (customer relationship management system, the place that remembers every customer and deal), a task is created for a sales person, and an automatic message thanks them. Later, the same CRM sends reminders and follow-ups. I explain why this matters in why your CRM must connect to WhatsApp in Nigeria, and you can see how I build it on my WhatsApp automation service.

POS, stock and accounting

A supermarket till records every sale. The integration sends the totals to the stock system, which reduces quantities and warns when items run low, and to the accounting tool, which records revenue and tax. The owner reads one report in the morning instead of comparing three sheets.

Delivery, maps and customer tracking

An order is placed. The system uses a maps API to calculate distance, sets the delivery fee, assigns the nearest rider, and sends the customer a tracking link. This is the backbone of the systems I build for food and courier businesses.

The APIs Nigerian businesses use most often

You do not need to know hundreds of APIs. A handful cover most of what Nigerian shops, schools and offices need.

Payments and bank data

Paystack, Flutterwave, Monnify, Interswitch and similar providers let you accept cards, transfers, USSD and wallet payments and send money out. Some services let you give each customer a dedicated virtual account number, so every transfer is matched to the right person automatically, which schools love. Others, such as Mono, let a customer give permission for you to see their bank statement, for lending and verification. I cover these in detail in my article for developers on building with Nigerian fintech APIs.

Messaging: WhatsApp, SMS and email

The WhatsApp Business Platform sends receipts, reminders and support replies from your system. SMS gateways, such as Nigerian providers that deliver to MTN, Airtel, Glo and 9mobile numbers, send codes and alerts. Email services send invoices and newsletters. Messaging is the most visible integration, because your customers see it every day. Use it carefully, with permission and useful content, or you will lose trust.

Identity and verification

Some businesses must confirm who a customer is: lenders, cooperatives, landlords, hotels and marketplaces. Verification providers offer APIs to check identity details such as BVN or NIN, or to compare a selfie with an ID. These involve strict rules on consent and data protection, and they cost per check. Do not collect identity numbers unless you must, and do not store them longer than needed.

Maps, delivery and location

Maps APIs calculate distance, estimate travel time and show a rider on a map, which is valuable in Lagos traffic and Abuja estates where a wrong turn costs an hour. Delivery companies also offer APIs to book a pickup and track parcels. This is how a small store can offer tracking without building a logistics company.

Accounting and business tools

Accounting tools, CRMs, calendars, spreadsheets and cloud storage all have APIs. They let you push daily sales to your accountant’s system, add new customers to a mailing list, or save signed documents into a folder. These are less exciting than payments, but they remove a huge amount of clerical work.

The four ways to connect your business tools

There is no single best method. The right one depends on how important the connection is, how often it runs and who will look after it.

1. Built-in integrations

Many tools already talk to each other. Shopify connects to payment providers, accounting tools link to banks, and a WordPress shop has plugins for Paystack and Flutterwave. Always check this first. It is the cheapest option and someone else maintains it. Its weakness is that you can only connect what the maker allows, in the way they allow.

2. No-code automation tools

Services such as Zapier, Make and n8n let you connect tools by drawing steps: “When a new row appears in this sheet, send a WhatsApp message and add a contact in the CRM.” They are excellent for simple, low-risk jobs and for testing an idea before you invest more. Their weaknesses are limits on how many tasks you can run, pricing in dollars, and difficulty handling complicated rules or money. I would never run a payment system on a chain of no-code steps without proper checks.

3. Custom API code

A developer writes code that speaks directly to the APIs. This is the most flexible and the most reliable route for important connections, such as payments, stock and customer records. You can build exactly the rules you need, handle errors properly and keep everything in your own system. It costs more at the start, and needs maintenance. This is what I do most often for clients who need it, through my custom software development work.

4. An integration hub or middleware

When you have many tools, a central hub can sit in the middle so that each tool only connects to the hub, not to every other tool. Think of a bus terminal: each route goes to the terminal, not to every other city directly. It keeps things tidy as you grow. It is overkill for a small business with three tools, but useful for a group with a website, a POS, an ERP, a CRM and a mobile app.

My usual advice is to start with built-in connections, use no-code for quick experiments, and move important flows to custom code once they prove their value. If you are also weighing rented tools against building your own, read my guide on SaaS versus custom software.

How to read API documentation without being a developer

You do not need to write code to judge whether a tool is easy to connect. You need to know what to look for on its developer page.

What good documentation includes

Open the developer pages of a service, for example the Paystack documentation, and notice how they are laid out. Good documentation has a getting started guide, a list of endpoints with sample requests and answers, a test mode, clear error messages, a page on webhooks, and a changelog that shows what changed and when. If a vendor has no public documentation at all, treat that as a warning.

Check the pricing and the status page

Two more pages tell you a lot. The pricing page shows what each request, message or transaction costs, and whether there are limits or tiers that will surprise you as you grow. The status page, if the vendor has one, shows past outages. If a provider has frequent problems and no honest record of them, your customers will feel them before you do.

Test mode and live mode

Every serious payment or messaging service gives you a test mode with fake money or fake messages. Your developer builds and tests everything there first, and only then switches to live keys. If someone offers to “just plug in live payments and see”, stop them. A test that costs real naira is a poor test.

Eight questions to ask about any API

1. Is there test mode and a full sample dataset?
2. How does authentication work, and can I limit what a key can do?
3. Does it send webhooks, and can I verify that they are genuine?
4. What are the rate limits, and what happens when I exceed them?
5. What is charged per request, per message or per transaction?
6. How are errors reported, and can a failed action be safely repeated?
7. How often does the API change, and how much notice do users get?
8. Is there real support in Nigeria hours, and how fast do they reply?

Bring this list to any developer and ask them to answer it before you commit to a tool. It takes an hour, and it can save you months.

How much do API integrations cost in Nigeria?

There are two costs: building the connection and running it. Many people only budget for the first.

Building costs

As at 2026, a simple one-way integration, such as sending a form to a CRM, can cost ₦100,000 to ₦300,000. A payment integration with proper handling of webhooks, failures and duplicates often costs ₦150,000 to ₦450,000. A two-way sync between systems, with rules and error handling, usually runs from ₦400,000 to ₦1.2 million. Connecting several systems, such as a POS, an ERP and accounting, can reach ₦1.5 million to ₦5 million or more. These are ranges I see, and every business is different.

Running costs

• API and message fees: SMS costs a few naira per message, and WhatsApp business messages are charged by Meta per message or conversation at rates that change, so check the current price list.
• Hosting: the small server that runs your connection, usually ₦10,000 to ₦40,000 a month.
• Monitoring and care: someone must watch for failures and update the code. Expect ₦30,000 to ₦100,000 monthly for a serious setup.
• No-code plans: often ₦15,000 to ₦80,000 a month, billed in dollars.

Do the sum before you decide

Take the hours of double entry you would remove, multiply by what your staff cost, and compare it with the build and running costs. If the payback is under twelve months, it is usually worth doing. If it is over two years, think again. The exception is any connection that prevents fraud or lost money, which is worth more than the time it saves.

A payback example

Go back to Funke. Her three evening hours were shared by two people. We connected her Paystack payments and order forms to a small system that updates stock, sends the rider a WhatsApp message and creates the receipt. It cost her about ₦420,000 to build and roughly ₦35,000 a month to host and monitor. The two hours a day she and her sister saved were worth more than ₦100,000 a month at the pay they would ask elsewhere, and the double-selling stopped completely. She recovered the build cost in about five months, and, more importantly, she started replying to new customers earlier in the evening instead of doing paperwork.

Security: keeping keys, customer data and money safe

An integration opens a door between systems. A careless door lets thieves in. Here are the rules I follow in every project.

API keys are passwords

A key lets software act on your behalf: take payments, send messages, read customer data. Never paste keys in WhatsApp, email or a shared spreadsheet. They belong in the server’s secret settings. Use separate keys for test and live, and change a key immediately when a staff member or developer who knew it leaves. Some keys can send money out. Guard those the way you guard your bank token.

Give each key the least power it needs

If a report tool only needs to read sales, give it a read-only key. If a service can be limited to certain IP addresses (the network addresses of your servers), do it. That way, a stolen key is far less useful to a thief.

Verify webhooks, and confirm before you trust

Anyone can send a fake message to your webhook address that says “payment successful”. Real providers sign their webhooks, and your code must check that signature before it does anything. It is also wise to ask the provider directly, “Is this transaction really paid?”, before you release goods. Never trust the message that comes back through the customer’s browser, because a customer can fake it. This single check stops a lot of online store fraud, and I describe the details for developers in the fintech article linked earlier.

Keep logs, but keep secrets out of them

Logs are the diary of your integration and you need them to solve problems. But logs must not contain full card details, passwords or secret keys, and they should not keep customer information forever. Decide what you record, who can read it and when it is deleted. A leaked log file can be as damaging as a leaked database.

Protect personal data

Every integration that moves customer names, numbers or ID information is handling personal data under the Nigeria Data Protection Act. Send only what the other system needs, keep records of what was shared, and do not store more than necessary. If you connect a tool you do not control, read its privacy terms first.

When integrations break: NEPA, timeouts and duplicate payments

Connections between systems fail. That is not a flaw, it is a fact of life, especially where networks drop and power flickers. A good integration expects failure and handles it calmly.

Retries and queues

Say your website tells your stock system to reduce a product, but the stock server is down for two minutes. A naive system loses that message. A good one puts the message in a queue (a waiting line), tries again after a few seconds, then after a minute, then after ten, and raises an alert if it still fails. Nothing is lost, and nobody has to remember to fix it.

Duplicates and the “safe to run twice” rule

Networks often send the same message twice. A payment provider may send a webhook again if it did not get a reply in time. Without care, your system could mark an order paid twice, send two receipts or credit a customer’s wallet twice. The cure is called idempotency, which just means an action is safe to repeat. Every payment gets a unique reference, and the system checks “Have I already handled this one?” before doing anything. It is the difference between a professional integration and a costly one.

Test the power cut on purpose

Do not wait for a real NEPA outage to learn what happens. Before launch, I switch off the internet during a test order, kill the server in the middle of a payment, and send the same webhook five times. Then I check that no money is lost, no customer is charged twice, and the system recovers by itself when the connection returns. Sometimes we find a problem at this step that would have cost the client dearly on a busy Friday.

Monitoring and alerts

Ask three things of every integration. Does it keep a log of what it sent and received? Does it alert someone when there is a failure? Is there a simple page where a non-technical person can see that it is healthy? A connection with no monitoring is like a generator with no fuel gauge: you find out when the lights go out.

When the other side changes

APIs change. A provider may retire an old version, change a field name, or add a new security rule. Good providers announce it months ahead. Your developer should read those announcements and keep your connection up to date, which is one more reason to have a maintenance plan. An integration is a living thing, not a one-time build.

A step by step plan for your first integration

Do not try to connect everything at once. Pick one painful handoff, fix it well, and learn from it. This is the order I follow with clients.

Step 1: choose the most painful handoff

Ask your staff, “Which copy and paste job do you hate most?” Choose the one that costs the most time, or causes the most mistakes. For Funke, it was moving paid orders into the stock sheet and telling the rider. That one connection saved her almost two of the three hours.

Step 2: draw the flow on paper

Write what happens now, one line per step, and who does it. Then write what should happen automatically. Mark what data moves: names, amounts, phone numbers, order numbers. Mark what could go wrong, such as a failed payment or an out of stock item. Fix any confusion in the process first. Connecting a messy process just makes the mess faster.

Step 3: build and test in a safe environment

1. Use test mode keys and fake customers.
2. Try the happy path, then the unhappy ones: wrong amount, repeated webhook, missing phone number, slow network.
3. Check the logs to be sure each step is recorded.
4. Let a staff member who will use it every day try to break it.

Step 4: go live small, then widen

Turn it on for one product line or one branch, watch it for a week, and compare it with the manual results. When the numbers match, expand. Keep the old method available for a short time in case of trouble, then retire it.

Step 5: write it down and name an owner

Document what the integration does, which keys it uses, where it runs and who to call when it fails. Name one person in your business as its owner. Without an owner, nobody notices when it stops.

A realistic timeline for a first integration

A first integration of this size usually takes four to six weeks from the first conversation to full use. Anyone who promises the same result in two days is either working on something trivial or skipping the testing.

Aisha manages a busy fast food outlet in Kaduna with two branches. Her tills, her delivery riders and her stock sheet were all separate, and she was closing her books at midnight every day. We connected only two things at first: the till to the stock system, and Paystack payment links to the order screen. Within a month she was closing at 6 pm. She said, “I did not know how much time I was giving to copying numbers until it stopped.” She later added the delivery tracking, but the first small win paid for everything after it.

Five integration mistakes I see again and again

These mistakes cost real money, and almost all of them are avoidable.

Integrating a broken process

If your process is unclear, an integration just moves confusion between systems faster. Fix the rule first: who approves a discount, when stock counts as sold, what happens to a failed payment. Then automate. The work I do on automating business processes always starts with the process, not the code.

Building a web of tiny connections

Ten separate no-code links, each made by a different person, become a tangle that nobody understands. When one breaks, nobody knows which. Keep a simple map of what connects to what, and consolidate when it grows.

Skipping the unhappy paths

Demos show what happens when everything works. Real life includes cancelled orders, partial payments, refunds, timeouts and typing errors. Ask your developer how each one is handled, and test them.

Letting one person hold all the keys

If a single freelancer holds every login and key, you are one resignation away from a crisis. Store secrets in a company vault, keep at least two people with access, and require documentation. I have watched an entire online store go offline because a developer’s personal email account, which owned the payment keys, was locked.

Forgetting the cost of change

Your business will change. New branch, new product, new payment gateway. An integration that is built with clean, separate parts is easy to change. A tightly stuck one is not. Ask early: “If I move from one provider to another next year, what would that cost?”

Key takeaways

• An API is the official way one program talks to another, and an integration uses APIs so your tools share information without retyping.
• Webhooks are doorbells: the other system tells you when something happens, which is faster and cheaper than checking again and again.
• The biggest wins are usually payment to order, website to CRM, POS to stock and accounts, and chat to CRM.
• Choose the method to fit the risk: built-in first, no-code for quick tests, custom code for payments and core rules, a hub when many systems join.
• Budget for building and running: simple connections cost from ₦100,000, and serious ones can cost millions, plus monthly care.
• Treat API keys like passwords, verify every webhook, and give each key only the power it needs.
• Design for failure: retries, queues, duplicate protection and monitoring keep your business safe when NEPA or the network misbehaves.
• Start with one painful handoff, test in a safe mode, go live small and name an owner.

Frequently asked questions

Next step: connect your first two tools

If your team spends hours every week copying data between WhatsApp, Excel, your payment gateway and your stock records, an integration will probably pay for itself in months. I can look at your tools, tell you which handoff to automate first, and explain the options and costs in plain English. See my software development services, browse my projects, or book a free consultation. You can also message me on WhatsApp from the site and describe the copy and paste job you hate most.