What’s Happening with the Employee API

November 7, 2018

Background

The Employee API is changing to support campus needs in conjunction with the UCPath project.   The Enterprise Integration Services (EIS) team is working with the UC Path team, the developer community, and functional owners to refine requirements and test the next version of the API.  The current version running in production, v (2), will be decommissioned in the near future.

What is different about Employee v(3) API?

Employee API v(3) is based on Enterprise Data Objects (EDO).  The contract for presenting data will be different, using the new EDO format, and endpoints will change.  You will need to review current data mappings to the Employee API v(2), and retrofit existing code to ensure it aligns to v(3). 

When will this occur?

Testing in DEV started April 16, 2018. Here is a general timeline for the Employee API.

Function

Target Dates

Deploy Employee API v3 to DEV

4/16/2018

Deploy Employee API v3 to TEST for Integration Testing

October 2018

Deploy Employee API v3 to UAT for Integration Testing

ETA - January 2019

Deploy Employee API v3 to PROD

ETA - March 2019

Decommission v2 in PROD

ETA - March 2019

Why is this changing?

Employee API v(3) provides a seamless transition to UCPath from a data integration perspective. When the data source transitions from the current UC Berkeley on-premise HCM to the UCPath centralized data source, the API contract and endpoints remain the same as defined in Employee API v(3) - your API clients will not need to change.

Stay tuned to the UCPath Tech Talk website for additional updates to the Employee API as it continues to evolve with the UC Path project initiative.