Troubleshooting Ceridian Dayforce tap in Connector Builder

Summary

The user is developing a tap for Ceridian Dayforce using the Connector Builder. They are able to retrieve the Bearer token successfully via HTTPS/No Auth POST but are facing issues using the token in subsequent GET requests.


Question

Hi. I’m developing a tap for Ceridian Dayforce, which is a payroll/hr platform. As the documentation suggests we should try the no-code Builder first, that’s what I’m using. It is able to successfully retrieve the Bearer token via HTTPS/No Auth POST (Form-encoded). However it is failing to then use the retrieved token in further GET requests.

I’m in Melbourne/Australia timezone. Is anyone available to troubleshoot with me?



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["ceridian-dayforce", "tap", "connector-builder", "bearer-token", "https", "post", "get", "troubleshoot"]