Thirteen facts about nine systems. And the 30 nobody publishes.
A register of what Australian small business software actually documents about its API — auth,
rate limits, pagination, webhooks, verification, retries, bulk, sandbox, data location and cost.
Every entry is the vendor’s own wording, fetched 1 September 2026 and linked. Where a vendor publishes
nothing, the cell says so.
The register in four numbers
9systems, all of which we have built against
87of 117 fields published by the vendor
30fields no vendor documents at all
0measured by us — see below, and it matters
How to read the register
Nine systems down the side. Thirteen fields across, though the wide table below shows the five
that change a design decision most often — the rest are on each system’s own page. Every value is
quoted from the vendor’s documentation and linked to the page it came from, so nothing here has to
be taken on trust.
The most useful cells are the empty ones. When a vendor does not publish its rate limit, that is
not a formatting problem — it means the first time anyone finds the ceiling is in production, on a
real business, usually on the busiest day of the month. We mark those rather than filling them in
with a number from a forum thread.
Everything was fetched on one day, 1 September 2026. Three entries were changing that week, which is
exactly why the date is on every cell rather than at the bottom of the page.
What we mean by tested
Two different claims get blurred together on pages like this one, so here they are separated.
Documented — what this page has
The vendor’s published behaviour, fetched, dated and linked. Anyone can verify it. It is
genuinely useful, and it is not a measurement.
Built against — what we can also say
We have implemented against all 9 of these in production. That tells you we have
solved each system’s problems before. It does not tell you a number.
Measured — what this page does not have
Observed limits under load, real failure modes, what breaks at what volume, date last tested.
That column is empty today. Publishing a plausible figure in it would make this whole register
worthless, because you would have no way to tell which cells were real.
The register
Five fields shown here. Each system’s page carries all thirteen, plus the vendor-flagged
constraints that actually change how you build.
Nine systems, five fields, fetched 1 September 2026 from vendor documentation.
Empty cells are absences in the source, not omissions here.
Three findings fall straight out of it. 1 of the nine has no webhooks at all,
which turns every integration with it into a polling loop with a running cost.
2 sends webhooks it does not sign, so the only safe pattern is to treat the
event as a hint and trust the follow-up fetch. And 6 of the nine publish where your
client’s data physically sits — two of them state plainly that it is the United States,
and none offers an Australian region.
Nine systems. The interesting part is always the three that were rerouted by hand.
Where ‘no API’ still has a path
Two of the nine are automation platforms rather than systems of record, and they exist precisely
because the answer to “does this thing have an API” is often no. Worth knowing what the fallbacks
actually are before concluding a system cannot be integrated.
A published export is an integration
A nightly CSV to a watched folder is unglamorous, hard to break, and enough for most reporting. It is
not real-time, and it is usually the right first step rather than the compromise.
Email is an interface
Systems that will not talk will still send a notification, a statement or a report. Parsing
those is fragile in a way an API is not — but it is a path, and sometimes it is the only one.
The other side may have the API
Integration needs one endpoint, not two. If the closed system can push a webhook or send a
file, the open system can do the rest of the work.
When the honest answer is no
Some systems genuinely cannot be automated without screen-scraping, and we do not build that —
it breaks on a UI change nobody told you about. We will say so and the engagement stops there.
System glue covers the shape of this work in more detail, and
the integration checker answers the narrower question of
whether we have built against both sides of a particular pairing.
Systems we haven’t tested yet
Everything not in the table above. Tradify, AroFlo, Fergus, Buildxact, Ascora, Reckon, Sage,
HubSpot, Salesforce, monday.com and every vertical product for a trade we have not worked in.
Some of them publish excellent documentation. We have not built against them, so they are not here.
That is a deliberately narrow rule and it costs us pages. It would be easy to read Tradify’s help
centre and add a row — but that row would say the same thing our
comparison pages say about products we have not
implemented, and this register is supposed to be the place where the bar is higher than that.
Tell us about a system we’re missing
If you run something not listed and you want to know whether it can be joined to the rest of your
stack, that question is free to ask and usually quick to answer. Ring
0403 475 099 or email
hello@kindraai.dev — we will tell you what its documentation
says, and whether the answer is a build, a platform, or leaving it alone.
The register is published under
CC BY 4.0 and available as
machine-readable JSON. Reuse it, including
commercially, as long as Kindra AI is credited and the fetch date travels with the figures — a
rate limit without a date is worse than no rate limit.
Objections
Is this just vendor documentation rewritten?
Partly, and deliberately. Every fact here is the vendor’s own published documentation — that is
the point, because it means you can check all of it against the link beside it. What is not in
any vendor’s documentation is the comparison: thirteen identical fields across nine systems,
fetched on one day, with every gap marked rather than quietly skipped. No vendor publishes a
competitor’s limits beside their own, and nobody at all publishes the absences.
Why aren’t more systems listed?
Because these are the nine we have implemented against. Reading a vendor’s documentation is
something anyone can do in an afternoon; we would rather the register only cover systems where
we have also had to make one work at two in the morning. It grows when our experience does,
which is slower and worth more.
Book a free Leak Check
20 minutes. We find where the money's going. No pitch.
