API’s returning the proper data values and understanding how to consume APIs can be a daunting task. Familiarity with the technical aspect of the applications used to support API’s will greatly reduce the time spent refactoring your application. Anypoint Exchange (also called WashU API Portal), and Postman are the two applications you will use to achieve that goal.
Integrators will also require a strong understanding of the data, what it means, and how to manipulate it in order to build a successful integration.
The Help Document page will provide that context. It separated by Technical and Functional documentation.
Anypoint Exchange How To
This document details all of the features of Anypoint Exchange, including each of the five Wash U APIs, their endpoints, and the technical specifications.
Getting Started with API’s
This document details what an API is, how Wash U consumes APIs, URL’s for test and production environments, details the sections within the endpoint, and data examples.
Person – Worker API Queries
This document provides information on important query parameters in the Person API including Future Dated Hires, Deletions, and Terminations.
Mulesoft API Mappings
This document provides technical details about each API (Person, Finance, Organization, Location, and Supplier) to assist integrators as they build out their integrations. Details include source and data type, and most importantly, the API Fields and the endpoints they are located at.
People In Workday
This document defines worker types and worker sub-types in depth so applications can better understand how people are managed in Workday.
Cost Center Concepts
WashU currently groups employees by department or division in HRMS and AIS. In Workday, employees are grouped by supervisory organization; fiscal responsibilities and financial transactions are grouped by cost center. This presentation explains these concepts and also details cost center hierarchy and cost center hierarchy rollup.
Common Worker Filtering
The Person API returns over 36,000 unique worker records. Some applications may require the entire WashU population, while others may only use a small fraction of that total. This document will detail various options to filter the population to the desired results for each application.