Tradify has no API. Here is exactly what that leaves you, from Tradify’s own pages.
Tradify publishes no API, no webhooks, no developer portal and no Zapier app. What it publishes is a set of CSV exports, a header-only job import, and first-party syncs to Xero, MYOB and QuickBooks Online. We have not built against Tradify. Everything here is its own help centre and pricing, fetched 3 September 2026.
What Tradify publishes about its API
- Documentation
- No. Tradify publishes no developer portal, API reference or OpenAPI specification on any of its domains. Its help centre has seventeen categories and none of them is API, developer, webhooks or Zapier. Tradify help centre, fetched 3 September 2026.
- Authentication
- Not published.
- Token lifetimes
- Not published.
- Rate limits
- Not published.
- When you exceed one
- Not published.
- Pagination
- Not published.
- Webhooks
- Not published.
- Event verification
- Not published — no payload signature scheme.
- Retry behaviour
- Not published — no retry policy.
- Bulk operations
- CSV only. Jobs, invoices, quotes, purchase orders and bills, customers, sites, suppliers, enquiries, timesheets and price lists export to CSV. Jobs import from a CSV template, header fields only — costs, labour, notes, files, appointments and invoices must be entered by hand. Bulk update is export, add an identifier, edit, re-import, and Tradify recommends against it. Tradify help centre — exporting your data, fetched 3 September 2026.
- Test environment
- A 14-day free trial with all features and no credit card. No developer or test environment is published. Tradify Australian pricing, fetched 3 September 2026.
- Data location
- Not published — the vendor does not say where the data is stored.
- Cost of API access
- Not applicable — there is no API to charge for. Plans are $48, $52 and $62 AUD per user per month excluding GST, with SMS at $0.20 a message and an Instant Website add-on at $19 a month. Tradify Australian pricing, fetched 3 September 2026.
Every line above is the vendor’s own documentation, fetched 3 September 2026, linked so you can check it yourself. 9 of the 13 fields are not published at all — those are marked, and they are the ones that cost you time. The full capability register puts this beside the other systems.
What the Tradify API does and does not allow
Per-user job management for small trade teams, now owned by The Access Group. Tradify publishes no API, no webhooks and no developer portal. Everything in and out is a CSV or a first-party accounting sync. We have not built against it.
Nine of the thirteen fields we track are marked not published for Tradify, and that is not a documentation gap in the usual sense. There is nothing to document. Tradify’s help centre has seventeen categories — Get Started, Jobs, Quotes, Invoices, Scheduler, Timesheets, Forms & Certs and so on — and none of them is API, developer, webhooks or Zapier (Tradify help centre, fetched 3 September 2026). Zapier’s own directory has no Tradify app to fetch.
We have not built against Tradify, and with no API there is nothing to build against in the usual sense. What follows is what Tradify does publish — exports, imports, syncs and prices — read the way an integrator reads it, fetched 3 September 2026 and linked. The ServiceM8 versus Tradify comparison covers the pricing crossover in detail; this page covers what you can and cannot move in and out.
What a no-API product is, honestly
A legitimate product decision, and for many of its customers an irrelevant one. Tradify is priced per user — $48, $52 and $62 AUD a month excluding GST on Lite, Pro and Plus, with a 14-day trial and no card required (Tradify Australian pricing, fetched 3 September 2026) — and aimed at small crews who need job management plus their accounting package and nothing else. For that business the absence of an API costs nothing.
It becomes the only thing that matters the day a third system enters the picture. A quoting tool, a customer portal, a dashboard, a stock system, an automation that is not Xero. On ServiceM8 those are buildable by anyone through a public API with 180 requests a minute and webhooks on nine record types (ServiceM8 webhooks, fetched 1 September 2026). On Tradify the answer is whatever Tradify ships, on Tradify’s schedule.
That schedule is public. Tradify’s 2026 release notes, current to 6 May 2026, record Xero sync fixes in April and nothing about an API, webhooks or Zapier (Tradify 2026 release notes, fetched 3 September 2026). If one is coming, Tradify has not said so anywhere we can link.
What you can get out: the CSV exports
More than you might expect, and less than you need for a clean exit. Tradify’s self-serve exports cover enquiries, jobs, invoices, quotes, purchase orders and bills, timesheet reports, customers, customer sites, suppliers and supplier price lists, all as CSV, plus five reports — Job Sheet, Job Financial, Productivity, Timesheet and Contact Tracing — downloadable as CSV from the Reports page (Tradify help centre, CSV downloads, fetched 3 September 2026).
What the exports leave behind is the part to know before you sign up, not before you leave. Job notes and files — photos and attachments — are not included in any export. Forms, certificates and service reminders cannot be bulk-exported at all. For a full copy of notes and files, Tradify’s instruction is to contact support (Tradify help centre, exporting your data, fetched 3 September 2026). For an electrician, the CoES and test sheets are in that second group.
As an integration surface, a scheduled CSV export is the first of the four doors on our custom and legacy page: dull, vendor-supported and one-directional. It is enough for reporting, for a dashboard, and for reconciling against the accounting package. It is not enough for anything that needs to know about a job while it is still happening.
What you can put in: a header-only job import, and a bulk update the vendor advises against
Jobs can be imported from a CSV template, self-serve, under Jobs > Options > Import Jobs from File. The template carries the customer — which must already exist — plus site, a reference of up to 100 characters, status, pricing level, categories, address, description, custom fields, assignment and start and end times in YYYY-MM-DD HH:MM:SS format (Tradify help centre, importing jobs, fetched 3 September 2026).
It is header-only. Tradify states that costs, labour, notes and files, scheduled appointments, staff members and invoices "will all need to be captured manually" after the import, and that customers, sites, statuses, pricing levels and categories cannot be created during it. A migration from another system therefore lands the shell of each job and none of its money.
Bulk updating existing jobs is possible by the same route — export, add a unique identifier to each row, edit, re-import with "Match existing jobs using" set to that field — and Tradify’s own article says "due to the effort and time involved to do this, we recommend against it" (Tradify help centre, bulk updates, fetched 3 September 2026). When the vendor tells you its own write path is not worth using, the honest reading is that there is no write path.
- KNDR·01Reporting and dashboardsYes, from scheduled CSV exports. One-directional, hours-stale, and enough for most owners’ Monday morning.
- KNDR·02Reconciliation to the ledgerYes, but through Xero, MYOB or QuickBooks rather than Tradify. The accounting package has the API; Tradify feeds it.
- KNDR·03Anything live, or anything that writesNo. There is no event when a job changes and no supported way to write more than a job header. This is the boundary, and Tradify draws it.
The accounting sync is the real integration, and it belongs to someone else
Tradify’s pricing page names accounting sync to Xero, MYOB and QuickBooks Online on every plan, and its features page names Stripe for payments and Google Calendar for scheduling (Tradify features, fetched 3 September 2026). Those syncs are real, documented in the help centre, and they are the way a Tradify business already participates in an integrated stack — indirectly.
That is the pattern we would build to. Tradify writes the invoice to Xero; Xero has webhooks on invoices, a published 60-a-minute limit and the rest of a proper API; the automation you actually want — debtor chasing, a cash-position report, a customer payment reminder — hangs off Xero, not Tradify. The job management system becomes an input to the ledger, and the ledger becomes the integration surface.
The limit of that pattern is timing. Nothing reaches Xero until Tradify syncs it, and nothing about the job before invoicing — the quote accepted, the tech on site, the variation raised — reaches anything at all. If your automation idea lives in that window, Tradify is the wrong platform for it and no amount of building changes that.
Ownership changed, and the privacy policy followed
The Access Group announced an agreement to acquire Tradify on 1 October 2024 (Tradify, joining The Access Group, 1 October 2024). Tradify’s privacy policy now names Access Workspace Inc of 251 Little Falls Drive, Wilmington, Delaware as the operator and does not state where customer data is stored (Tradify privacy policy, fetched 3 September 2026). Data location is one of the nine fields marked not published above.
For a plumbing or electrical business this is a note, not a problem. For a business handling health or disability information it is the same question we raise on every page: ask before connecting, and get the answer in writing. Compare Microsoft 365, which publishes that an Australian tenant’s mailbox content stays in Australia.
What acquisition tends to change, over years, is the product roadmap. An API could arrive under new ownership; equally, the product could be folded into a larger suite. Neither is announced. What is published is a per-user price, a CSV export and no developer surface, and that is what a decision should rest on today.
What we have not built, and what we would do instead
We have not implemented against Tradify, and with no API there is nothing conventional to implement against. Nothing on this page is a Kindra measurement. It is Tradify’s own help centre, pricing and privacy pages, read closely and linked so you can check each line.
If you are on Tradify and want automation, the honest first question is whether the thing you want lives after the invoice — in which case we build it against your accounting package and Tradify stays exactly as it is — or before it, in which case we will say plainly that the platform does not support it, and the conversation becomes whether to change platforms. Choosing job management software is the guide for that second conversation.
Either way, we would rather tell you which of those two you are in during a Leak Check than after a quote. Twenty minutes, and the answer is usually obvious from the first job you describe.
The questions people actually ask.
01You have never used Tradify. Why is there a page about it?
Because people on Tradify ask us for automation, and the honest answer — there is no API, here is exactly what that leaves — is more useful than silence or a sales pitch. Everything on this page is Tradify’s own published material with a link and a date. We have said in the first line and the last section that we have not built against it. If Tradify publishes an API, this page changes and says when.
02Can’t you just automate the Tradify web app directly?
We could, and we will not. Driving a product’s screens with a user’s login is the one approach we refuse on every legacy system, for the reasons on the custom and legacy page: it needs a real person’s credentials stored where a program can read them, and it breaks silently the day a button moves. Treasury’s 2023 screen-scraping review put the credential-sharing concern in plain words, and it applies here.
03Should we move off Tradify to get an API?
Not for the API alone. Tradify may be the cheaper product for your shape — two people running eight hundred jobs a month pay about a third of what they would on ServiceM8, on published prices — and a cheaper product with a CSV export beats a dearer one with an API you never call. Move when a specific automation you need cannot be done any other way, and cost the move against what the automation earns. If that sum is close, stay.
Stop bending.
Start shipping.
Bring the one flow that keeps costing you a Tuesday afternoon. We map it live and tell you what we'd build, what we wouldn't, and what it costs.