workwing-io
WorkWing provides field service management software with an open API, enabling companies to schedule jobs, track work, and integrate with CRM systems. The platform offers mobile apps for technicians, a unified dispatch board, and customizable reporting without per-user fees. It supports free trials and paid plans starting at £79 per month, targeting teams that need coordinated field operations and seamless data flow.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles workwing-io the way a machine reads it — 28 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — workwing-io scores 41.0/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
the company serves an API surface but requires credentials before any description of it can be read
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is workwing-io's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://docs.workwing.io/openapi.json→ HTTPhttps://api.workwing.io/mcp→ HTTP 401https://workwing.io/→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-11-06 · rubric v0.27.0
Put this on your own site. The badge is drawn live from workwing-io's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/workwing-io/"
title="workwing-io on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/workwing-io.svg"
alt="workwing-io Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/workwing-io/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/workwing-io/"
title="workwing-io on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/workwing-io/card.svg"
alt="workwing-io Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile workwing-io
Each block below is one kind of artifact we hold for workwing-io. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
workwing-io Assignments API
Assigning resources to jobs
workwing-io Brands API
Brand configuration (read-only)
workwing-io Context API
API key introspection, capabilities, and organisation info
workwing-io Custom Fields API
Custom field definitions: the schema (keys, labels, types) for job, customer and resource custom fields. Read them for discovery, create and update them to define the fields an ...
workwing-io Customers API
Customers and their notes and attachments
workwing-io Health API
Service health check
workwing-io Integrations API
Running configured integrations and receiving their callbacks
workwing-io Job Schedules API
Recurring job schedules (create, lifecycle)
workwing-io Job Status History API
Job status change audit trail (read-only)
workwing-io Job types API
Job types (read-only). The collection is `job_templates`, and a job's `template_id` points at one.
workwing-io Jobs API
Jobs and their notes, parts, attachments, status, and custom fields
workwing-io Location History API
GPS traces and job segments (read-only)
workwing-io Locations API
Customer locations and their notes
workwing-io OAuth API
OAuth connection management
workwing-io Parts Catalogue API
Parts catalogue and brand-specific pricing (read-only)
workwing-io Projects API
Projects: jobs that own a pool of jobs, with their window, crew, and progress. A project is a job, so it is updated with `PATCH /v1/jobs/{jobId}` and crew is added with `POST /v...
workwing-io Resource Groups API
Resource groups (read-only)
workwing-io Resources API
Resources (your engineers and other field staff) and their notes, skills, attachments, and working hours
workwing-io Schedule API
Resource scheduling, availability, and conflicts
workwing-io Skills API
Skill definitions and categories (read-only)
workwing-io Workflows API
Bulk operations and multi-step workflows
Scroll within the panel for all 21 ·
Agent Skills 1
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
getting-started
AGENT SKILLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Workwing Io Webhooks
ASYNCAPISpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
workwing-io API Rules
SPECTRALSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for workwing-io — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/workwing-io · machine-readable index on apis.io
This is an independent, third-party profile of workwing-io, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.