Configure Connection
Ceridian Dayforce guide
Arrange Dayforce API access, configure tenant and account details in NIM, and validate employee data for downstream user provisioning.
Before you beginDirect link to Before you begin
API documentation is available through the Dayforce developer portal and requires login. Consult the authenticated documentation and Dayforce Support to create API access for your environment.
NIM requires Tenant URL, Company ID, Client ID, Username, and Password.
Obtain tenant and account detailsDirect link to Obtain tenant and account details
- Sign in to the Dayforce developer portal and review the API setup requirements for your environment.
- Work with Dayforce Support or your administrator to provision access to the employee data required by your process.
- Obtain the Tenant URL, Company ID, Client ID, and account Username and Password for the integration.
- Confirm the account's employee data permissions and store the credentials securely.
Enter the connection settingsDirect link to Enter the connection settings
- In NIM Studio, open Systems > Overview and add a Ceridian Dayforce system, or select the existing system.
- Open Connection, enter the following settings, and save.
| NIM setting | Value |
|---|---|
| Tenant URL | The Dayforce API tenant address supplied for your environment, using the format expected by the Connection screen. |
| Company ID | The company identifier supplied for the integration. |
| Client ID | The client identifier authorized for API access. |
| Username | The username of the account authorized to retrieve employee data. |
| Password | The corresponding password for that account. |
Test employee retrievalDirect link to Test employee retrieval
-
Select Test Connection. NIM attempts to retrieve employees using:
GET /V1/Employees -
If the test fails, verify the Tenant URL, Company ID, Client ID, account credentials, network access, and API permissions with your administrator or Dayforce Support.
-
Collect the employee data required by your process and confirm that the expected records are present.
-
Validate employee matching and field mappings before using the data for downstream user provisioning.
The connection test checks employee retrieval. Validate other collections and field access required by your process separately.