Workday: REST call to a report

[Jonathan F]

We are pulling information from Workday and avoiding their plugin (based on what we see in this community forum) and their SOAP API (based on how needlessly complicated it is), and so we landed on using their Rest API to pull what Workday calls Custom Reports. So, we are using System Web Services > REST Message to call Workday.

Results:

- Workday has IP Whitelisting for security purposes, so I configured the REST Message to use the MID Server set up for our integrations

- I updated our firewall rules and confirmed that the traffic from the MID Server to the Workday server is not blocked

- I have the correct Basic Auth credentials, and have confirmed that I can reach Workday using Postman from my device AND using the logs in ServiceNow that it is sending an identical header as I'm using from my device that works

- We temporarily removed the IP Whitelisting rules and attempting to call directly from ServiceNow to Workday

However, these REST requests continue to receive a 401 unauthorized message from Workday. Does this problem sound familiar to somebody? If so, what did you do to fix the situation?

Thank you for your time and consideration.

[Mike Patel]

Also make sure the username and password is correct in SN. I have exact same header and works fine for me.

[Jonathan F]

I have re-pasted the username and password and also "hard coded" the Authorization=Basic [garbled] into the field on multiple occasions instead of using the Basic auth profile field in the Authorization tab. This appears not to be the problem.

[Jonathan F · Accepted solution]

It turns out that it was the configuration error was on Workday's side. I finally got access to view their login attempt logs, which included more detail about why the request was rejected. It showed that the update he thought he applied was not actually applied because he had to submit a few more requests to apply the change. After applying the change to the IP Whitelisting, the request goes through for the report.