Every page in this directory grades how open a platform is — whether other software can talk to it. This page explains what that actually means, in jobsite terms, so you can judge any software pitch yourself. No jargon you can’t translate.
An API is a service window. Your software — Jobber, ServiceTitan, QuickBooks, whatever runs your shop — keeps everything behind a counter: customers, jobs, invoices, schedules. An API is the window where another program can walk up, show its credentials, and ask for specific things in a specific format: “give me yesterday’s new leads,” “mark job 1042 complete,” “create an invoice for this customer.”
Without a window, the only way in or out is a person — someone at a keyboard, copying and pasting, exporting spreadsheets, re-typing. That’s why some shops can automate follow-up and some can’t: it’s not the automation tool, it’s whether the shop’s software has a window, and how wide it opens.
An API key is the badge that lets a program use the window. Think of it as a jobsite key card: the office issues it, it opens only certain doors, and if someone loses it, the office cancels that card — nobody has to change every lock in the building.
That last part is the whole point. A key is not your password. Your password opens everything, including payroll and banking. A proper API key opens only what it was issued for. When a vendor or an app asks for your actual account password instead of using a key or a sign-in approval screen (that’s called OAuth — you approve access on the vendor’s own page and can revoke it later), that is a red flag. Legitimate tools almost never need your password.
A webhook is a phone call. The moment something happens — a lead comes in, an invoice gets paid — the platform itself calls the other program and says “it happened, here’s the details.” Follow-up can start in seconds.
A scheduled sync is a delivery route. The other program drives by every 5 minutes, every hour, or once a night and asks “anything new?” It works, but there’s always a gap between the event and the reaction.
Why it matters: a new-lead text that arrives in 30 seconds books jobs. The same text arriving tomorrow morning is a courtesy. When a platform has no webhooks, “instant” automations built on it are really “eventually” automations — no matter what the salesperson called them.
Bridge apps are general contractors for software. Zapier and Make sit between thousands of programs and pass information across: “when this happens in App A, do that in App B.” For simple jobs — a new lead lands in a spreadsheet, a text goes out when a form is filled — they’re genuinely useful and cheap.
Know their limits before you build a business on them:
In this directory, a Zapier or Make listing counts as evidence for the bridge rung only. It does not prove a platform has a real API.
The most common surprise in this directory: the API exists, the docs are public — and your plan doesn’t include it. Vendors gate API access behind higher tiers, paid add-ons, or partner programs. It’s rarely mentioned on the pricing page’s main grid.
The second surprise: only an admin on the account can create API keys, approve connected apps, or turn the feature on. If your office manager’s login can’t see the settings page, the project stalls until the account owner shows up. Before any automation project, answer two questions: which plan are we on, and who is the admin?
A vendor who answers all five cleanly is selling you a platform. A vendor who dodges them is selling you a cage with good marketing.
Free AEO Checker — Is your website ready to be recommended by AI search? Get a readiness score from the signals on your own site.
Free Snapshot — Find where leads and money leak — missed calls, slow lead response, stale quotes, unpaid invoices — and see which connections your current software can actually support.
Related platform guide: the AEO Check API — our own checker as an API