Dayforce RESTful services use the POST verb to create an employee balance transaction.
Overview
Consuming applications can use the POST Employee Balance Transactions request to create new employee balance transactions in Dayforce.
The URL for POST operations uses the following base URL:
https://www.dayforcehcm.com/api/CompanyName/V1/EmployeeBalanceTransactions
To create a balance transaction, a unique identifier (XRefCode) must be provided. This is done within the data that is sent for processing (referred to as the request body). The XRefCode must be generated by the requester and it must be unique. It is the consuming application’s responsibility to assign a unique identifier (XRefCode) to the balance transaction when it's sent in a POST operation. Dayforce web services will return an error if the XRefCode provided in the request body matches the value of an existing balance transaction in Dayforce. If this occurs, the consuming application raises an error requesting manual intervention.
Important: This request writes data into Dayforce. When using this request, be sure that the consuming application/requester is using the correct Dayforce instance (test or production). Watch out for inadvertently updating the wrong instance of Dayforce (for example, adding test data to a production instance).
Parameters
IsValidateOnly* (boolean)
- Used to specify that all of the validations need to be performed without committing any changes.
- Use this parameter to control whether committing information to your instance of Dayforce is your responsibility.
https://www.dayforcehcm.com /api/CompanyName/V1/EmployeeBalanceTransactions?isValidateOnly=true
Request Body
The request body contains the values that need to be inserted. The request body should be structured so that it can be interpreted by Dayforce web services. Therefore, consuming applications should use the JSON structure that they retrieve when using the RESTful Get Employee Balance Transactions request. See Get Employee Balance Transactions.