Authenticate to the Workiz API and create a job or lead
domain: developer.workiz.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Enable the Developer API add-on in Workiz (Settings > Integrations > Developer) to generate an API token and secret
Build requests against the REST base URL, including the API token in the URL path per Workiz's documented pattern
POST to the job-create endpoint with customer, address, and job-type details to create a new job record
POST to the lead-create endpoint instead if the work hasn't been qualified/scheduled yet, so it enters Workiz's lead pipeline rather than as a scheduled job
Use the corresponding get/update endpoints to fetch job or lead details and keep status in sync as the record progresses
Assign users/technicians and update lead status (e.g. marking a lead lost or active) through the documented update endpoints as the record moves through your pipeline
Known gotchas
Job creation and lead creation are distinct endpoints (job/create vs lead/create) — decide up front which pipeline stage you're integrating with, since converting one to the other isn't a simple status flip via these endpoints
The API secret's exact placement/use in signed requests is not fully documented publicly — verify current auth requirements directly against the developer portal for your account before assuming a specific signing scheme
Confirm current base-URL and versioning on developer.workiz.com at integration time, since third-party guides may lag the official portal
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?