Workwell Technologies website screenshot

Workwell Technologies

Workwell Technologies, Inc. is a Carlsbad, California workforce management company backed by Battery Ventures, best known for its uAttend cloud-connected time and attendance platform and uPunch punch clocks. uAttend pairs biometric time clocks (fingerprint, facial recognition, RFID, voice control) with cloud software for time tracking, scheduling, overtime alerts, and optional payroll processing for small businesses. The WorkWell Technologies API exposes employee, timecard, and punch data from uAttend accounts over HTTPS with API-key authentication, supporting payroll and HRIS integrations.

Workwell Technologies publishes 3 API contracts indexed on the APIs.io network: Punch Reports API, Timecards API, and Users API. Tagged areas include Company, Workforce Management, Time Tracking, Attendance, and Payroll.

The Workwell Technologies catalog on APIs.io includes 1 Spectral governance ruleset.

Workwell Technologies’ developer surface includes documentation, API reference, support, engineering blog, and 5 more developer resources.

16.3/100 emerging ▬ flat Agent 23/100 agent aware saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
1 published contract
CompanyWorkforce ManagementTime TrackingAttendancePayrollHuman ResourcesTime ClocksBiometricsScheduling

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the Employment & Payroll regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Workwell Technologies It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/workwell-technologies/"><img src="https://apis.io/badge/workwell-technologies/card.svg" alt="Workwell Technologies on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
9 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/workwell-technologies/apis.yml: open an issue on github.com/api-evangelist/workwell-technologies to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

MarketPositionDepthRegistered MCP serverDeclares compatibility
Biometrics Testing (biometric recognition vendors, identity verification depth) standard 17.2 (thin) - -

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (published)

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Workwell Technologies Punch Reports API

Raw punch records across a date range

Workwell Technologies Timecards API

Per-user, per-pay-period timecards

Workwell Technologies Users API

User records for the uAttend account

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Workwell Technologies API Rules

52 rules · 50 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Workwell Technologies Uattend Overlay

3 actions · update · workwell-technologies-uattend-openapi.yml

DERIVED

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Operate 1

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: workwell-technologies
name: Workwell Technologies
description: Workwell Technologies, Inc. is a Carlsbad, California workforce management company backed by Battery Ventures,
  best known for its uAttend cloud-connected time and attendance platform and uPunch punch clocks. uAttend pairs biometric
  time clocks (fingerprint, facial recognition, RFID, voice control) with cloud software for time tracking, scheduling, overtime
  alerts, and optional payroll processing for small businesses. The WorkWell Technologies API exposes employee, timecard,
  and punch data from uAttend accounts over HTTPS with API-key authentication, supporting payroll and HRIS integrations.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-11-06'
  method: derived
image: https://uattend.com/wp-content/uploads/2019/07/uAttendLogo-01.svg
url: https://raw.githubusercontent.com/api-evangelist/workwell-technologies/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- battery-ventures
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Workforce Management
- Time Tracking
- Attendance
- Payroll
- Human Resources
- Time Clocks
- Biometrics
- Scheduling
apis:
- aid: workwell-technologies:workwell-technologies-punch-reports-api
  name: Workwell Technologies Punch Reports API
  description: Raw punch records across a date range
  humanURL: https://uattend.zendesk.com/hc/en-us/articles/48783008798875-uAttend-API
  baseURL: https://api.workwelltech.com
  tags:
  - Punch Reports
  properties:
  - type: OpenAPI
    url: openapi/workwell-technologies-punch-reports-api-openapi.yml
  - type: Documentation
    url: https://uattend.zendesk.com/hc/en-us/articles/48783008798875-uAttend-API
- aid: workwell-technologies:workwell-technologies-timecards-api
  name: Workwell Technologies Timecards API
  description: Per-user, per-pay-period timecards
  humanURL: https://uattend.zendesk.com/hc/en-us/articles/48783008798875-uAttend-API
  baseURL: https://api.workwelltech.com
  tags:
  - Timecards
  properties:
  - type: OpenAPI
    url: openapi/workwell-technologies-timecards-api-openapi.yml
  - type: Documentation
    url: https://uattend.zendesk.com/hc/en-us/articles/48783008798875-uAttend-API
- aid: workwell-technologies:workwell-technologies-users-api
  name: Workwell Technologies Users API
  description: User records for the uAttend account
  humanURL: https://uattend.zendesk.com/hc/en-us/articles/48783008798875-uAttend-API
  baseURL: https://api.workwelltech.com
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/workwell-technologies-users-api-openapi.yml
  - type: Documentation
    url: https://uattend.zendesk.com/hc/en-us/articles/48783008798875-uAttend-API
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: X-MCPServerCandidate
  url: mcp/workwell-technologies-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Overlay
  url: overlays/workwell-technologies-uattend-overlay.yaml
- type: Website
  url: https://workwelltech.com/
- type: Documentation
  url: https://uattend.zendesk.com/hc/en-us/articles/48783008798875-uAttend-API
- type: APIReference
  url: https://uattend.zendesk.com/hc/en-us/articles/48783008798875-uAttend-API
- type: Support
  url: https://uattend.zendesk.com/hc/en-us
- type: Blog
  url: https://uattend.com/blog/
- type: PrivacyPolicy
  url: https://uattend.com/privacy-policy/
- type: Login
  url: https://v2.trackmytime.com/login/login.aspx

Workwell Technologies API — frequently asked questions

Does Workwell Technologies have an API?

Yes. APIs.io lists 3 APIs from Workwell Technologies, including Workwell Technologies Punch Reports API, Workwell Technologies Timecards API and Workwell Technologies Users API.

Is there an OpenAPI specification for the Workwell Technologies API?

Yes. APIs.io indexes 3 OpenAPI specifications for Workwell Technologies, each linked for download from this page.

How do I authenticate with the Workwell Technologies API?

Workwell Technologies uses bearer-token authentication.

Is the Workwell Technologies API ready for AI agents?

Workwell Technologies has a Kin Score of 16.3 out of 100 (emerging) and an Agent Readiness score of 23.4 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/workwell-technologies"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/workwell-technologies/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/workwell-technologies/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.