Technical mapping study
UKG API to stored procedure mapping
A procedure-level assessment of every unique operation in the UKG HCM OpenAPI index, compared with 5,425 supplied SQL Server procedures.
OpenAPI documents do not disclose backend procedure calls. Strong leads have direct naming or SQL evidence. Possible matches need code or runtime confirmation. No match means the CSV did not support a defensible assignment.
Assessment at a glance
198 endpoints have a credible lead
Duplicates across the 24 files were consolidated by HTTP method and path. The remaining endpoints include 136 learning, onboarding, and recruiting operations with no supported procedure match.
Distinctive procedure name, integration-staging purpose, or direct resource correspondence.
Related procedure family or shared generic handler. Verify the exact call before relying on it.
No sufficiently supported candidate in the supplied CSV. This is not proof that no procedure runs.
Coverage by API domain
Where the evidence is concentrated
Full endpoint register
Search the mapping evidence
Open any row to see the rationale, shared SQL fields, source specifications, procedure alternatives, and modification date.
| API request | Domain | Candidate procedure | Assessment | Evidence |
|---|
No endpoints match these filters
Clear one or more filters to widen the result set.
The mapping data could not be loaded
Refresh the page to try again.
How the assessment was made
Evidence before assignment
- 01
Consolidate the specifications
All 24 linked JSON files were retrieved. The 696 operation entries became 353 unique method-and-path pairs, with duplicate source files retained in each row.
- 02
Compare names and intent
Paths, operation IDs, summaries, and HTTP methods were compared with procedure names. Resource-specific reads and writes ranked above broad family similarity.
- 03
Check SQL support
Procedure bodies were checked for API parameters and response fields. The evidence dialog shows shared fields when present, but field overlap alone did not establish a strong lead.
- 04
Leave weak guesses unresolved
Endpoints without a defensible name or SQL connection remain unmatched. A strong lead is still an inference, not proof of the production execution path.
Recommended verification
Confirm strong leads against application code or a controlled SQL Server Extended Events trace. Capture one request per route, correlate the service call with rpc_completed and sp_statement_completed, then record the actual procedure chain. Pay particular attention to generic code-table handlers and versioned Kronos procedures.
Source register
Specifications and procedure data
API definitions came from the UKG HCM OpenAPI index. Procedure names, schemas, timestamps, and SQL bodies came from the supplied stored_procedure info.csv.
Show all 24 OpenAPI source files
Four files contain schemas or webhook definitions but no path operations: audit-1.json, audit.json, pro-hcm-webhook-events.json, and pro-hcm-webhook-eventsjson.json.