Notes
At last, the data feeds from the new Workday tenant are available! We’re now sourcing our data from the same place being used for end-to-end testing in Workday, so our data set is more current and more complete. You’ll mostly see this as new records and associations being available, but there may also be some records that no longer exist. If you have hard links to any particular resources, you may want to verify that they’re still what you expect.
We’ve enabled the ‘Try this API’ feature that’s built into the Developer Portal. This lets you query the API right from the browser without needing to install any software on your computer. It’ll provide a quick and easy way for new users to get familiar with the API before they start building integrations on it.
You can now see data about our ETL jobs to verify that we’ve got the most current data. The new /diagnostics/etlRuns/current path will get you the most recent run. We currently run our updates once a day, but could switch to a more frequent schedule in the future if there’s demand for it.
In the next sprint, we’re looking at doing some backend work around our data sources. We’re switching from the native Workday APIs to custom-built reports, which will be easier for us to feed into our ETL process and offer a lot of customization options that the APIs don’t have. Users of the API shouldn’t see any change from this, but it’s helping to make sure the product is supportable as we move ahead.
API changes
- Added a new
diagnostics/etlRunsendpoint to see details about our ETL job that loads data from Workday diagnostics/etlRuns/currentis a shortcut to the most recent job