Skip to main content
This page prevents assumptions about functions that are not exposed by the current public OpenAPI contract.

​
Available capabilities

​
Not exposed by public v1

The current contract does not define public operations for:
  • tenant creation, update, or deletion
  • API-key management through the API
  • employee deletion
  • changing an employee’s work email through the employee patch operation
  • transferring an assigned employee to another tenant through employee patch
  • order creation
  • changing a final order decision through the decision endpoint
  • incident deletion or reopening
  • division deletion
  • payroll export generation or deletion
  • general idempotency keys
  • bulk mutation endpoints
  • multiple sort fields
  • webhook registration or public event subscriptions
  • a public stage or sandbox base URL

​
Important behavioral limitations

  • dryRun=true validates current production state; it is not a sandbox.
  • Pagination is not documented as a snapshot.
  • X-Request-ID does not deduplicate writes.
  • A successful dry run does not reserve state.
  • A resource may appear not found when it is outside the API-key scope.
  • Download metadata can exist while fileName is null, meaning no file was produced.
  • Order and incident lifecycle states include server-managed transitions outside the exposed mutation operation.

​
Polling model

The current public contract is client-initiated. Integrations discover changes by calling collection endpoints with suitable filters and checkpoints. If a needed business capability is not listed, do not infer it from internal portal behavior. Use the established JobHandy integration channel to clarify customer-specific alternatives.
Last modified on August 27, 2026