You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Workers API replacing Emps. Understanding future state

Summary:

I understand that the /emps rest api call will be deprecated as of 23D? If so, I am looking to understand the best way to find all the fields which emps was providing once it goes away.

Content (required):

Hello community,

From what I understand, the current "get an employee" rest api call is going to be deprecated as of 23D. I'm talking about emps:

/hcmRestApi/resources/11.13.18.05/emps

The replacement being provided for this call is workers.

/hcmRestApi/resources/11.13.18.05/workers

Currently, these calls return drastically different things. Most notably, instead of including most information in the root "items" list, the workers call stores this information in the child elements instead. So in order to get to most fields in the workers api it will require a call to 2 endpoints rather than just 1 like it did with emps. And that's on the simple side (for this call). From what I could piece together, in it's current state, in order to get an employee's manager's name, you would have to call workers -> workRelationships -> assignments

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!