Kickserv API Guide for Contractors

One-line verdict: A real public API for customers and jobs — premium plans only, XML instead of JSON, and no estimates, invoices, or payments anywhere in the vendor’s endpoint list. Openness: 3 / 5 — rated 3 because Kickserv documents genuine read/write endpoints, capped by the premium-plan gate, the older XML format, and a money surface that simply isn’t there.

The connection that works

Rung 1 — Direct connection. Kickserv’s own documentation (a live Swagger page) covers “version 1 of the Kickserv Public API,” implemented “via XML over HTTP in a RESTful manner.” XML is the older dialect — your builder translates; what matters is that the doors exist and are documented endpoint by endpoint. Sign-in is HTTP Basic authentication with an employee’s API token, found in the employee management section and sent on every call; note the operational quirk the vendor documents: the token is used as both username and password, and it changes when that employee’s password changes — so the connection belongs to a person, and their password reset is your integration outage. Every address carries your account slug. One more vendor sentence worth knowing before you budget: Kickserv provides the API “for use by your own internal or external development team” and states it “cannot assist with implementation or development.”

The verified endpoint list, exactly as the vendor publishes it: Customers — full read/create/update/delete, plus customer notes the same way; Jobs — full CRUD, plus job notes and time entries (full CRUD) and a create-only job-charges endpoint; Employees read/create/update; Tasks create/read-one/update/delete; Items — read-only, list only. Read that list for what it does not contain: no estimates, no invoices, no payments endpoints at all. A job charge is not an invoice, and this page won’t call it one.

Plan gate, in the vendor’s words: “API access is available to premium plans only.” (Kickserv’s own 2018 changelog says the API came at no extra cost to subscribers — older copy that conflicts with the current docs; the current docs govern.) No webhook documentation and no rate limit appear in the vendor’s API docs.

Bridge apps: no Kickserv listing was found on Zapier at all. On Make, only a community-built app exists — Make itself says it can’t provide complete documentation for it and doesn’t maintain it. There is no verified official bridge; the direct API is the road.

Can automate

• Customer and job sync — both are fully writable and deletable through documented endpoints, so Kickserv can mirror your CRM or intake tool record for record.
• Field time capture — time entries on jobs are full CRUD, so hours recorded elsewhere can land on the right job.
• Notes that travel — customer and job notes are API objects, so context captured on a call or a form can be attached where the crew will see it.
• Crew records — employees can be read and maintained from connected systems.

Can’t automate

• Estimates, invoices, or payments — no endpoints exist in the vendor’s list. Not gated, not hidden — absent. Estimate follow-up and invoice chase cannot be built on this API.
• Instant alerts — no webhooks are documented; connections poll on a schedule.
• Anything on a non-premium plan — the vendor gates the whole API to premium plans.
• A rate limit to plan against — UNVERIFIED. None is stated in the vendor docs; a careful builder paces requests anyway.
• JSON or OAuth — the documented format is XML over HTTP with Basic auth. Modern-tooling assumptions don’t apply.
• Zapier recipes — no listing exists. Third-party claims otherwise are not a Zapier app page.

Hidden gate: The API only turns on if you’re paying for a premium plan — the cheaper plans can’t use it at all. And pick the token’s owner carefully: it lives on an employee’s record and resets with their password.

Build fit — what this platform supports well

• Speed-to-Lead — workable on premium: a lead becomes a customer and a job through documented creates, on a polling rhythm.
• Missed-Call / After-Hours Capture — works: a captured call creates the customer and the job.
• Estimate Follow-Up / Invoice Chase — not on this API: no estimate or invoice objects exist to follow up against; the work runs on our messaging layer and your accounting tool.
• Review Engine — like every platform here, Kickserv has no verified reviews API, so the review ask runs on our system triggered by a job-completion signal checked through the API.

What this means for your shop

If you run Kickserv on a premium plan, the operational core — customers, jobs, notes, time — connects honestly, and a builder comfortable with XML can wire it into your other tools. The boundary is money: quotes and billing live outside this API’s reach, so any pitch that starts with Kickserv invoice automation is pitching a product the vendor’s own endpoint list doesn’t contain.