Getting Started & Support

Originally posted by Sukal Mondal on September 22, 2025 at 12:41 PM. FYI: Delete Quick Entry via “Delete Employee Punches”—gotchas? Heads-up: You can remove Quick Entry items via the Delete Employee Punches endpoint (not an obvious mapping).Ask:Any specific filters you rely on to avoid accidental deletes?Do you soft-delete first (flag) then hard-delete? What’s your rollback plan? 

Originally posted by Sukal Mondal on Edited November 5, 2025 at 11:10 AM. 🧠 Did You Know?You can integrate with Dayforce using RESTful Web Services — giving you the power to access, manage, and extend Dayforce data programmatically.The Dayforce RESTful Web Services Developer Guide provides everything you need to get started:How to connect securely using API authenticationHow to read and write data via REST endpointsBest practices for handling data structures and building custom integrationsWhether you’re extending functionality or embedding Dayforce into your own applications, this guide is your essential resource.👉 Explore the full guide here : https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide Have a question or tip about RESTful integrations? Start the conversation in the Integrations/API group <link stripped through migration>

Originally posted by Sukal Mondal on November 4, 2025 at 1:49 PM. Troubleshooting Earning Statement API Errors Problem (Real-Life Example) A client trying to pull Earning Statement PDFs via API could retrieve the statement XRefCodes but hit errors when fetching the actual PDF files. The Web Services role looked correct, leading the team to suspect an issue with PGP key configuration. 💡 Expert Tip If you’re fetching PDFs via API:Make sure the PGP key has been generated and loaded properly.Confirm whether the key is maintained by your implementation or integration team.Check that your role has “Earning Statement” permissions enabled under Web Services access. 

Originally posted by Sukal Mondal on November 10, 2025 at 10:10 AM. 🔧 Share Your Favorite Postman Trick! Working with Dayforce APIs in Postman? We all have that one trick that makes things faster or easier — whether it’s auto-refreshing tokens, switching environments, or validating responses. 💬 Share your favorite Postman tip or setup hack in the comments and help fellow developers work smarter!

DetailsThe following section outlines various best practices to help you configure your integrations correctly and to ultimately help you to avoid making some common mistakes.Filters are configured to return a subset of records that meet specific criteria. To determine where to apply a filter in your configuration, consider the following questions:What is the scope of your filter? Should your filter apply to the entire set of records in your output or only to some of the data in the file? How many records do you expect to be in one output file?Refer to the following scenarios for more information about where you should apply a filter in your configuration:When a filter should to be applied to the entire set of records, and you are expecting multiple records in the output: You must configure a filter on the topmost array parent in your mapping configuration. This is likely to be the case most of the time. This also applies to integrations that are configured to use the character separat

General Information Q: What are Dayforce Open APIs?A: Open APIs are a term used to describe the RESTFul APIs Dayforce makes available for data exchange between external system and Dayforce.Q: Who is the intended audience for Dayforce Open APIs?A: APIs may be applicable to many different personas, such as business analysts, technical implementers and consultants, software developers and product managers. The audience is any consumer that wishes to have real-time data exchange integrations between Dayforce and other external systems.Q: Is there a cost to use the Dayforce API?A: Currently there is no cost for using Dayforce Open APIs integrations. Getting started building API Integrations Q: How can I get access to an environment to begin using Dayforce Open APIs?A: Access to an environment is based on your relation to Dayforce. Dayforce customers and partners have access to non-production environments which can be used to enable API access for development and learning purposes. Organizat

This guide provides step-by-step instructions for configuring Dayforce to enable report retrieval via OData. This guide provides comprehensive instructions for administrators and users on configuring Dayforce to enable report retrieval via OData, detailing how to set up the application and ad hoc reports for OData use, establish connections with analytical tools like Microsoft Excel and Power BI, and understand important feature considerations including security, rate limits, and error messages for unsupported filter conditions. To learn more click here. 

The following section outlines various best practices to help you configure your integrations correctly and to ultimately help you to avoid making some common mistakes.All outbound Integrations in Integration Studio source data from one of the available HCM Anywhere APIs, such as the Employee Bulk or the Analytics Data Connector (Dayforce Reports). Additionally, inbound integrations can use an external API as a source.Review the following topics before you configure an API sourced integration:API ParametersAPI Parameters limit what data is returned when the API is called. Common parameters include Pay Period Start and End Dates and Employee or Pay Group Reference Codes.The following are best practices for populating parameters for common HCM Anywhere APIs in Integration Studio:Employee Bulk APIThe Export Period controls the scope of information pulled. The options are outlined on the Dayforce Developer’s Network. It is recommended that you review the options carefully, and run a test t

The following section outlines various best practices to help you configure your integrations correctly and to ultimately help you to avoid making some common mistakes.This topic covers some general tips and tricks for streamlining and configuring integrations in Integration Studio. Saving your IntegrationIt is strongly advised that you periodically save your integration, especially when you are working on very large or more complex integrations. Saving periodically can help reduce the likelihood of losing your work.Capitalization UsageWhen configuring expressions, use the =~ symbol for case-insensitive comparisons. Alternately, use = if the comparison should be case sensitive.You should always double check the capitalization of any source field names and field paths in your expression when the output is not as expected.Mapping a Source Array to a Destination ArrayIntegration Studio links source and destination arrays using a heuristic that is accurate for the majority of configuration

For any questions, issues, or assistance related specifically to the Dayforce Developer Community portal, its features, or content, please reach out to our dedicated support team.How to Submit a Query:To ensure your query is addressed promptly, please send an email with a detailed description of your issue or question to:dayforcedevelopercommunitysupport@dayforce.comOur community administrators will review your request and respond as quickly as possible.

General Availability & AccessWill the new reporting become default, or can we stay on classic reporting? Both classic reports and new reports will co-exist for a period of time. Advance notice will be given before classic reporting is sunsetted.Will the new reporting eventually be mandatory? Yes, the classic reports will continue to coexist for a period of time, and the potential retirement dates will be communicated well in advance.As a Client Admin Role, should I see the 'Report' option? Yes, if you are a Client Admin Role, you should see 'Report'. If not, submit a support ticket.If I give other roles access to the new reporting, will they still have the option to use classic or new? Yes, that is correct.Report Functionality & FeaturesWhy can't we "double click" to edit any longer? What was the reason for removing? The double-click feature was removed to improve accessibility and will be brought back in future releases. Double-click to open is also planned for a future releas

General InformationIs Integration Studio part of the Core HR module or an add-on? Please reach out to your CSM or AE to confirm.Building IntegrationsWhat can I do to avoid "N/A" in a column that causes my integration to fail? If "N/A" is coming from Dayforce data, you can set a default value in Integration Studio (advanced editor) for fields with no data.How do I add two lines of headers to a file? I click "Include Headers in Output," but it only sends one line. You would need to use the Segmented output format option and create two header parents.Can you include a header and trailer on a fixed-width export? Yes, if you just need one header and one footer you can use the regular Fixed Width Output option. If you have multiple, you will need to use the Segmented Fixed Width Output option.Is the "Event Driven HR Changes (Outbound) Connector" similar to an API Web Hook? The connector leverages Dayforce's HCM Anywhere Event Services. Whenever the integration runs, it collects all events th

IntroductionWhen building integrations, data flows, or transformations, developers often encounter repetitive scripting needs. Instead of writing expressions from scratch each time, the IDL Expression Library provides a central collection of reusable snippets for common scenarios.Think of it as your toolbox of ready-made expressions for string handling, control flow, transformations, and error handling. Why Use IDL Expressions?Handle edge cases: Many client and customer scenarios cannot be configured directly in the UI. IDL expressions bridge this gap by providing precise control over data transformations and business rules.Save time: Avoid reinventing the wheel by reusing tested patterns.Improve consistency: Standardized expressions reduce errors across projects.Enable flexibility: Expressions are modular and can be combined for complex workflows. Structure of an ExpressionEach expression in the library follows a consistent format for clarity and reuse:Name: A short, descriptive title

The following section outlines various best practices to help you configure your integrations correctly and to ultimately help you to avoid making some common mistakes.This topic covers some common configurations in Integration Studio.Return Contact Information from Contacts ArrayThe Employee Bulk API includes the Contacts array which, by default, includes all phone and email addresses stored in the Contact Information section of the People record. To return a single item from the Contacts array, you need a unique identifier to map the appropriate record.Home PhoneWhen the field is mapped to Contacts > Items > ContactNumber, you can configure a Choose Record filter on the ContactInformationType XRefCode.Business EmailSimilar to the choose record configuration for the HomePhone field, you can limit the specific Electronic Address returned by using the ContactInformationType XRefCode. Important: The Pick from list sorted newest to oldest and Pick from list sorted oldest to newest o

This Dayforce SOAP Web Services Developer Guide provides comprehensive documentation for developers on integrating with Dayforce using SOAP web services. It outlines how to connect to the platform, utilize various web service operations for data exchange, and leverage Dayforce's functionalities within custom applications and integrations.To learn more click here.

The following section outlines various best practices to help you configure your integrations correctly and to ultimately help you to avoid making some common mistakes.Group Your DataIt’s recommended that you configure your integration as much as possible before you enable grouping. This includes configuring the destination structure, destination field formats, and mappings.When grouping is enabled, Integration Studio marks all child fields and children of immediate object parents as Keys or Totals. By default, all nonnumeric fields default to Keys, and all numeric fields that use Aggregation as their source default to Totals. All other numeric fields are defaulted to Keys.These designations are shown in the application for your review and can be changed, if needed. You can easily change a field from a Key to a Total by clicking the action icon beside the field and then Mark as Total. Similarly, you can change a Total to a Key by selecting Mark as Key.Create a Custom Format for Strings