Workiz API Guide for Contractors

One-line verdict: A genuine, self-serve API for jobs and leads — just don’t expect it to touch your invoices. Openness: 3 / 5 — rated 3 because Workiz documents a real REST API with read/write on jobs and leads, but it sits behind a Developer API add-on and its object list stops before estimates and invoices.

The connection that works

Rung 1 — Direct connection. Workiz publishes a REST API reference and an OpenAPI spec. Access starts in your own account: turn on the Developer API add-on (Feature Center → Add-ons), then generate your API Token and API Secret in the Developer API settings. It is not an OAuth sign-in — the token travels in the request address and the secret in the request itself — so whoever holds those two values holds the keys; store them like passwords. The verified surface: Jobs read and write (create, update, assign, unassign), Leads read and write (create, update, assign, mark lost, convert a lead into a job), Team and Time Off read-only, and one narrow money write — adding a payment (cash, credit, or check) to a job. Customer details live as fields inside the job and lead records; there is no separate customers object.

One honest limit: Workiz documents no webhooks for the direct API. Nothing in Workiz calls your other systems the moment something happens — connections poll on a schedule, or use the bridge.

Bridge apps: Workiz has a real Zapier app — triggers for New Job, Job Status Change, Job Is Done, New Lead, and Lead Status Change (all polling, not instant), and actions to Create Job and Create Lead. Workiz’s own help center documents the Zapier route. On Make, only a community-built app was found, so we would not rest a critical workflow on that route.

Can automate

• Speed-to-Lead — new leads can be created in Workiz automatically from your website forms, ads, or answering service, and lead status changes can kick off follow-up in your other tools.
• Lead-to-job conversion — converting a lead into a job is a verified API action, so a won lead can become a scheduled job without re-typing.
• Job updates — jobs can be created, updated, and assigned from connected systems, and job status changes are visible to automations.
• Payment recording — a payment taken elsewhere can be added to the job in Workiz (cash, credit, or check).

Can’t automate

• Invoices through the API — UNVERIFIED. There is no invoices endpoint in Workiz’s published API spec. Reading invoices, creating them, or reacting the moment one is paid is UNVERIFIED — invoice-chase automation cannot rest on the direct API today.
• Estimates and quotes — UNVERIFIED. No estimates object appears in the vendor spec.
• A standalone customer database sync — UNVERIFIED. Customer details ride inside job and lead records; there is no customers endpoint to sync against.
• Instant event alerts — no webhooks are documented; Zapier’s triggers poll, so “the second it happens” automations carry a few minutes of lag by design.

Hidden gate: The API is locked behind a Developer API add-on you have to switch on first — and even then it only covers jobs and leads, not your invoices. If a builder’s quote assumes invoice automation on Workiz, the quote is wrong.

Build fit — what this platform supports well

• Speed-to-Lead — strong fit: lead creation and lead status are both real, verified API surface.
• Missed-Call / After-Hours Capture — works: a captured call can become a lead or a job in Workiz automatically.
• Estimate Follow-Up — weak on the evidence: no estimates object is documented, so follow-up would key off job status instead of the quote itself.
• Invoice Chase / AR — not on the direct API: invoices are UNVERIFIED; payments can be recorded onto a job, but the chase itself runs on our messaging layer.
• Review Engine — like every platform here, Workiz has no verified reviews API, so the review ask runs on our system triggered by a job-completion signal (Zapier’s “Job Is Done” trigger can supply it).

What this means for your shop

If you run Workiz, lead and job automation is genuinely buildable today — turn on the add-on, generate the credentials, and keep them guarded. Just draw the line where the vendor’s own spec draws it: jobs and leads yes, estimates and invoices unverified. A builder who shows you the spec page before quoting is a builder you can trust with the keys.