Skip to main content
Developer Communities Admin
Community Manager
September 30, 2026

Dayforce Recruiting APIs with reports

  • September 30, 2026
  • 0 replies
  • 6 views

Originally posted by Hanu Indrakanti on September 30, 2026 at 9:57 AM.

 

Hi Everyone,

We're currently fetching Dayforce Recruiting candidate data through reports, as there is no dedicated API for candidate information. We've hit a few limitations and would appreciate your guidance on the recommended approach.

 

What we're observing:

 

1. Multiple rows per candidate

A report returns one row per combination of job requisition, application status, contact method and additional field. For example, a single candidate with two job requisitions returns 10 rows. This makes it difficult to reliably determine one current record for the candidate.

 

2. Status dates don't identify the latest status

The effective date for application status appears to be stored at day level (start or end of day). When a candidate's status changes more than once on the same day, several statuses share the same date, and we can't tell which one is the current status.

 

3. Additional fields aren't identifiable

In reports, custom fields appear with generic names such as AdditionalField1 and AdditionalFieldIdList rather than their display names. We can't identify which field is which, and since each additional field adds rows for the same candidate, it compounds the issue in point 1.

 

Our questions:

 

1. Is there an API, or another supported method, to fetch candidate information together with the current application status for each job requisition? The current status per application, rather than the status history.

2. Is there a timestamp with time-of-day precision for status changes that reliably identifies the latest status?

3. Is there a way to retrieve additional/custom field definitions (display names mapped to their IDs), either in reports or through an API?

4. Are there any event notifications or webhooks for candidate status changes (for example, offer accepted or hired) that we could use instead of polling reports?

5. If reports remain the recommended approach, are there best practices for designing the report so it returns one row per candidate or per application?

 

We're looking for a reliable way to fetch candidate information along with the candidate's latest status.