Workwell Technologies · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the WorkWell Technologies API (uAttend)

3 actions 3 updates update extends openapi/workwell-technologies-uattend-openapi.yml

Generated by API Evangelist Written by API Evangelist tooling for Workwell Technologies's API. It is a proposal applied on top of the contract, not a document Workwell Technologies publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-providerx-apievangelist-notesx-apievangelist-paginationx-apievangelist-key-distribution

Targets 3

$.info

$.paths['/reports/punch'].post

$.components.securitySchemes.ApiKeyAuth

OpenAPI Overlay

overlay: 1.0.0
info:
  title: API Evangelist enhancements for the WorkWell Technologies API (uAttend)
  version: 1.0.0
  x-apievangelist:
    generated: '2026-07-21'
    method: generated
    source: openapi/workwell-technologies-uattend-openapi.yml
extends: openapi/workwell-technologies-uattend-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-provider: workwell-technologies
    x-apievangelist-notes: >-
      Spec generated by API Evangelist from the provider's published help
      center documentation; the provider does not publish a machine-readable
      contract. All endpoints use POST with JSON bodies, including reads. The
      documentation's section heading says "GET /user" but every method row
      and curl example uses POST, which is what this spec models.
- target: $.paths['/reports/punch'].post
  update:
    x-apievangelist-pagination: >-
      Page-based pagination via UsePaging/PageSize/PageNumber (0-indexed);
      EndDate must be within 3 months of StartDate.
- target: $.components.securitySchemes.ApiKeyAuth
  update:
    x-apievangelist-key-distribution: >-
      Keys are issued manually by WorkWell Technologies support via ticket, and
      the AWS API Gateway may enforce IP allowlists (403 explicit deny is a
      network restriction, not a key problem).