To ensure the best experience for all customers using web services, Dayforce expects customers to adhere to the following guidelines when designing their consuming applications and using Dayforce web services. Dayforce reserves the right to charge for overages or interrupt service if a client’s use of the web services features deviates from these guidelines.
Dayforce doesn't charge for the use of web services, provided the following conditions are met:
- You use the available documentation, sample applications, and tools to develop your application without the engagement of Dayforce resources; and
- Your consuming application adheres to the following standards for acceptable use:
- Consuming applications should be designed for system-to-system integration and not to directly populate a user interface or a mobile app.
- The number of records retrieved should be optimized using a changes since the previous request approach. This also applies to the design of the reports used with
Get Reportrequests. Get Employeerequests shouldn't return more than 1,000 employees per request. See the table Frequency of web services calls based on request type, immediately following this list.Get Reportrequests shouldn't return more than 1,000 rows per request.- You should use web services development frameworks that can handle additions to existing response objects without interrupting web services processing in production applications. Examples of such frameworks include Microsoft .NET and Java with the Apache CXF framework.
| Description of request | Calls to be made no more frequently than |
|---|---|
SOAP GetEmployeeXRefCodes - Requests for employees who were updated within a specific timeframe |
Every 15 minutes |
SOAP GetEmployeeXRefCodes - Requests other than for updated employees |
Every 2 minutes |
SOAP GetReport, OpenReportPages, and CloseReportPages |
Every 15 Minutes |
| RESTful requests for employees who were updated within a specific timeframe | Every 5 minutes |
| All other requests | No restrictions |
Important: Dayforce reserves the right to charge for overages and, or, to interrupt service if your use of Dayforce web services deviates from these guidelines.
As Dayforce continues to enhance our web services offerings, new data entities and or elements might be added to existing response objects. Dayforce doesn't consider the addition of new data entities and, or, elements to be a break in backward-compatibility.
When selecting your development frameworks, be sure that they support these types of additions without causing failures in your existing consuming applications. Though you might choose to use other frameworks, doing so might result in production web services applications returning errors and possibly failing to operate.