Obtain credentials for an Oracle HCM Cloud integration user with appropriate data roles, then authenticate using Basic Auth or OAuth 2.0 client credentials to get a Bearer token.
Construct the workers resource URL: https://{instance}.oraclecloud.com/hcmRestApi/resources/{version}/workers.
Issue a GET request to the workers endpoint; use the limit and offset query parameters for pagination.
Use the expand query parameter to include child resources inline (e.g., expand=workRelationships,names,emails) rather than making separate follow-up calls.
Append /describe to any resource URL to retrieve its full schema, available fields, and supported child resources.
Known gotchas
The API version is embedded in the resource URL path — Oracle increments this with releases; pin to a specific version and test before upgrading to avoid breaking changes.
expand can return very large payloads; request only the child resource collections you need, and consider whether fetching sub-resources individually is more efficient for large worker populations.
Oracle HCM REST APIs use HTTPS with Basic Auth in many configurations, but some Oracle Cloud environments enforce OAuth — check your instance's security policy before choosing an auth method.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp