ADP Workforce Connector Request for Time Cards endpoint.
AnsweredWhich application or service?:
What type of connector? (SaaS, Database, File or Event Source):
Additional details: Currently data are only being loaded through team-timecards end point. Requesting to add data using timecards too.
We want to use the timecard data along with the remuneration to derive the labor cost. We won't be able to do it accurately if we dont have the timecards endpoint.
-
Official comment
Hi David,
Thank you for your feature request regarding the ADP Workforce Connector. Could you provide more details on the use case for the time-cards endpoint and the analytical goals you aim to achieve with it?
Best,
Sandeep -
We are trying to get time-cards data from ADP but looks like it is not included on the current endpoints available. We want to get the actual time/labor that is recorded within the time cards.
These are the current endpoints inlcuded in the connector
GET /hr/v2/workers
GET /hr/v2/workers/{aoid}
GET /hr/v2/workers/{aoid}/leaves
GET /time/v2/workers/{aoid}/team-time-cards
GET /time/v2/workers/{aoid}/time-off-details/time-off-balances
GET /time/v2/workers/{aoid}/time-off-details/time-off-requests
GET /payroll/v2/workers/{aoid}/pay-distributions
GET /core/v1/event-notification-messages
DELETE /core/v1/event-notification-messages/{message_id}
We want to include time-cards so we can use the data for a more accurate timekeeping. -
Hi Sandeep,
We are currently attempting to utilize the time-card endpoint to calculate actual labor costs by differentiating between regular and overtime hours worked by an employee, in conjunction with their corresponding hourly pay rate.
Thank you.
-
Hi Sandeep,
We are currently attempting to utilize the time-card endpoint to calculate actual labor costs by differentiating between regular and overtime hours worked by an employee, in conjunction with their corresponding hourly pay rate.
Thank you.
----
The message above was sent last week. Can I please get a follow up?
Please sign in to leave a comment.
Comments
4 comments