The parts counter
Small Business API Integrations, Explained in Words You Can Use on the Phone
An API is a parts counter. You do not walk into the warehouse and rummage. You ask at the counter for a specific thing, in the format the counter expects, and it hands you that thing. Software does the same with other software, and that is nearly the whole secret.
November 9, 2026 · 10 min read
The short answer
An API is the documented way one piece of software asks another for information or tells it to do something. A small business API integration uses it so a form can create a customer, or a paid invoice can update the books, with nobody retyping. DataCram's custom integrations start at $575, depending on complexity, and go live the same day. Rented connectors like Zapier are worth trying first.
On this page
Stay at the parts counter for a minute
Keep the picture. The warehouse is someone's software: QuickBooks, Stripe, your job system. It has everything in it, and they would very much prefer you stayed out. The counter is the API. It is open to anyone with an account card, it has a printed list of what you can ask for, and it answers the same way every time. Ask for part 418 and you get part 418. Ask for "that blue thing from last time" and you get a polite refusal.
An integration is a standing arrangement with the counter. Each time a customer pays, your system walks up and says "mark invoice 2207 paid." It does this at 3 a.m. It does this during your kid's recital. It does not misread a seven as a one. What it replaces is you, at the kitchen table at 10 p.m., retyping one screen into another and hoping that your eyes hold out.
That is why this is usually the first piece of custom technology worth buying at a very small business. You replace nothing. You keep the products you like and pay for the small piece of work between them. The custom software overview puts this beside the other options, and the first test on whether you need custom work at all still applies: do you actually retype this, and how often?
Seven words you will hear from a vendor, translated
Nobody needs to learn to code to run this conversation. You need to understand enough to spot a wrong answer. If your job software is ServiceTitan, our owner's guide to its API lists seven questions that expose one. These words come up in nearly every call about connecting software, usually in a tone that suggests you should already know them. Now you do.
| At the counter | Why you might care | |
|---|---|---|
| API | The counter itself | Ask "is it documented and public?" No public API often means no integration without the vendor's help |
| Endpoint | One item on the counter's list: customers, invoices | If the thing you need is not on the list, the API cannot give it to you |
| Key or token | The account card you show | Treat it like a key to the shop. It stays on the server, never in a web page |
| OAuth | You tell the counter, in person, that this courier may collect for you | You approve a consent screen and do not hand over your password |
| Webhook | The counter phones you when your part comes in | Much better than checking every five minutes, and instant when it works |
| Rate limit | Only so many requests an hour | It matters when loading years of old records, and rarely after that |
| Sandbox | A pretend warehouse for practice | Lets a builder test without touching your live books |
QuickBooks makes a tidy example. Intuit's developer documentation, read November 6, 2026, describes a public REST Accounting API that works on entities such as customers and invoices. Its authorization page says apps connect through an OAuth 2.0 server, and customers grant permission through a consent flow. So you click approve, the courier gets a card, and nobody ever emails your password around. If a builder asks for your QuickBooks password, ask why.
What very small companies usually connect first
The best candidates share a shape. Something happens in one system, the next step is always the same, and a human adds nothing by copying it across. Look for the job you do with two windows open. If you need to think while you do it, it is a poor candidate, or at least needs a step where you approve what the machine prepared.
Website form to job software
A lead lands as a customer record, with no copy and paste. For trades, see ServiceTitan, Jobber and Housecall Pro.
Paid invoice to the books
Stripe says it is paid, QuickBooks hears about it. Stripe, QuickBooks and a CRM together needs some rules about who is in charge.
Booking to calendar
A customer picks a time, the calendar blocks it, and a reminder goes out. See AI appointment scheduling, which mostly needs rules, not AI.
Several tools to one page
Your Monday numbers pulled into a single dashboard, which only reads and is hard to hurt.
Job status to the customer
Status changes, and the customer sees it in a portal or a message, in place of a phone call to you.

Before buying anything new, check that your plan permits this. Vendors gate integrations by tier. Intuit's pricing page says, as of November 2026, that third-party integrations are not currently available on the QuickBooks Free plan. A connection you were counting on can vanish behind an upgrade, so ask before you sign up for anything, and read the software integrations guide if you are choosing products from scratch.
A rented connector or a custom one
Rented connectors are the honest first move, and they beat us on price for simple jobs. Zapier is the one most owners have heard of. Set up a free account, connect two apps, and see whether the idea works at all before paying anyone, including us. If it does and it stays reliable, you are finished. Vendor prices are as of November 2026.
| Rented connector | Custom API integration | |
|---|---|---|
| Starting cost | Zapier's Free plan: 100 tasks a month | From $575, depending on complexity |
| Ongoing | Professional from $19.99 a month billed annually for 750 tasks, or $29.99 billed monthly; Team from $69 or $103.50 for 2,000 | Hosting and upkeep; ask for the figure |
| When it goes live | When you finish setting it up | The same day |
| Good at | Simple one-way steps between popular apps | Your own rules, matching records, unusual fields |
| Weak at | Logic that grows into a tangle of branches | Anything simple enough that a connector would do it |
| Who fixes it | You, usually at an inconvenient moment | Whoever you agreed on, and agree in writing |
The usual reasons to move on are specific. Task counts rise until the bill passes what the job is worth. A step fails silently and you learn about it from an angry customer. The connector cannot match records the way you need, so you end up with two of every customer. Or the app you need has no connector. Those are good reasons. "Zapier seems unprofessional" is not, and no customer will ever know or care.
How an integration goes live the same day
People brace for a long project because software projects have earned that reputation. A connection between two documented APIs is a different animal. We put them live the same day. Most of the thinking takes place before anyone starts, and the owner's part amounts to one sentence and a few clicks.
- 1
Write one sentence
"When a Stripe payment succeeds, mark the matching QuickBooks invoice paid." If it needs an "and also," write a second sentence and choose which one comes first.
- 2
Confirm your plans permit it
Check each product's tier and that it has an API. Five minutes on the phone rules out most nasty surprises.
- 3
Approve access yourself
You click through each vendor's consent screen, or create a key in your account. You are the owner, so the connection should belong to your company's accounts rather than the builder's.
- 4
Test with a fake record
Run a pretend customer and a one-dollar payment, in a sandbox where the vendor offers one. See that it arrives correct and arrives once.
- 5
Switch it on and look at it tomorrow
It goes live that day. Next morning, compare a few real records by hand. Then set up the alert for when something fails.
What breaks a year from now, and the boring list that prevents it
An integration is a promise between two companies that have never met you, and either one can change. Nobody quotes for this part, so we will write it down. Most of these failures are small, and fixing them takes minutes. The cost is in not noticing for six weeks. Silence is the failure mode: the invoices just stop arriving, and nothing turns red.
- The person who approved it leaves. Some connections live under one user's login. Remove the bookkeeper's account and the sync dies. Connect it through an owner or a company account.
- A plan changes. You downgrade to save a little money, and your integration was a feature of the plan you left.
- The vendor updates its API. Fields get renamed and old versions get retired. Vendors announce this, in emails sent to whoever registered the account, so keep that inbox in use.
- Someone renames something. Change "Complete" to "Finished" in your job software, and a rule that was watching for the old word watches forever.
- A card expires on the hosting account. Nothing dramatic happens at first, and then everything happens at once.
The cure is an alert that fires when a run fails and a monthly glance at a few records. Our hosting and maintenance starts at $55 a month for a website, and we will say if your connection fits with that. Keep a one-page note naming each connection, what triggers it and who to call. That page matters more than the code, because it is what anyone would read first after you, or we, have forgotten how it works.
Silence is the failure mode: the invoices just stop arriving, and nothing turns red.
To check whether the time is worth buying back, use the savings calculator, or time the task by hand. The integrations service page has the detail, our pricing shows the rest, and the section for very small businesses sets out the wider case. Kairos, the booking widget we built and run, depends on connections like these, so a failed one is our problem too. Call (210) 346-0848 with your one sentence.
Questions owner-operators ask
Search the vendor's name plus "API documentation" or "developer." A real API has a public documentation site with a list of what you can read and write. If you find only a sales page saying "integrations available," ask support which plan includes API access and whether it can create records or only read them. Get that answer in writing.
It can be, if access is approved through the vendor's own consent screen, keys stay on a server, and the connection has only the permissions it needs. Be careful with anything asking for your password. Start with one-way connections that send data in a narrow, tested format. Review connected apps in your accounting account once a year and remove any you no longer use.
We put API integrations live the same day. The steps that matter are short: a one-sentence description, confirming your plans allow it, your approval on the vendor's consent screen and a test record. A rented connector like Zapier can be working the same afternoon if you set it up yourself. Either way, check real records the following morning.
With an API request, your system asks a question whenever it wants. With a webhook, the other system tells you the moment something happens. It is the difference between phoning the parts counter every hour and having them call you when the part comes in. Good integrations often use both, plus a daily check that nothing got missed.
Look for a scheduled export, an email notification or a rented connector, each of which can stand in with less reliability. Ask the vendor whether an API is planned, and treat the answer as a sales statement. If that tool sits at the center of your work and offers no way to get data out, weigh that when renewal comes around. It may be time to switch.
Keep reading
- One home per recordConnecting Stripe, QuickBooks and a CRM: Who Holds the Truth About WhatConnecting Stripe, QuickBooks and a CRM without double entries: which system owns each record, the fee math that trips your books, and the wiring order.
- Small, and yoursCustom Software for Microbusinesses: Small Tools That Retire the SpreadsheetDashboards, portals and integrations from $575, for owners who run the business from a phone and a spreadsheet, and the rented tools to try first.
- Criteria, not a countdownThe Best Software Integrations for a Small Service Business: Six Tests Instead of a Ranked ListWhich software integrations a small service business needs: follow one job, find the retyping, then run six tests. Rented connectors and custom prices.
- One owner, one phoneWeb Design for One-Person Businesses: What You Need and What to RefuseWebsite design for one-person businesses: the short page list, what to refuse to pay for, and fixed prices from $1,500, or when a builder plan is better.
- The build sideSmall Business Website Development: Who Holds the Keys When the Builder LeavesWebsite development for independent contractors: who owns the code, domain and accounts, what custom means at $1,500, and what you must maintain yourself.
- Probably not. Sometimes yes.iOS App Development for Small Businesses: When an iPhone App Earns Its KeepWhen an iPhone app makes sense for a very small company, what from $3,750 buys, Apple's fees and rules as of 2026, and what to try before you build.
- Everything in MicrobusinessSee the section
From the Insights desk
- 7 Signs Your Website Is Quietly Losing You CustomersA website rarely fails loudly — it just quietly lets customers slip away, and you never see the ones who left. Seven signs yours is leaking, from slow mobile loads to stale listings to no conversion tracking, and the fix for each.
- AI Agents vs. Plugins: Why Athena CMS Hires AgentsA plugin adds a feature and waits for someone to use it. An agent has a name, one job and a schedule, and it does the work. Seven reasons Athena CMS hires agents instead of installing plugins, where a plugin is still the right call, and how to pick your first agent.
Tell us the one sentence
Name the two systems and what should happen between them. A person replies with whether a free connector will do, or what a custom connection costs. Those go live the same day.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.