Sign in to Dayforce

The connector needs four values — Host, Client Namespace, Username, and Password. Your Username and Password come from a dedicated Web Services user you create; Host and Client Namespace identify your tenant. All steps below are performed by a System Administrator using your existing Dayforce sign-in, provided by your organization — not the Web Services account you create below.

Go to [https://www.dayforcehcm.com/mydayforce/login.aspx](https://www.dayforcehcm.com/mydayforce/login.aspx).

Dayforce sign-in page at mydayforce/login.aspx

Enter your Company ID, then click Continue to username.

Your Company ID is your Dayforce tenant identifier — the same value as the Client Namespace you collect later (found in Company > Settings > General).
It is assigned when your organization is provisioned; if you do not know it, your organization's Dayforce administrator can provide it.

Enter your Dayforce username and password to sign in.

These are your own existing Dayforce account credentials, not the Web Services account you create below.
If you do not have a Dayforce login or System Administrator access, request it from your organization's Dayforce administrator.

Get your Username and Password

Your Username and Password are a dedicated Web Services user account. Create a role scoped to the actions you use, then create the user and assign that role. Enable only what is required — granting more access than necessary is a security risk; never reuse an employee or admin account.

Go to System Admin > Roles and create a new role. On the General tab, give it a unique Name and Reference Code (avoid spaces and special characters), and attach your Web Services Password Policy.

Do not rename the role once it is used by the integration — this can break the connection.

On the Features tab, expand HCM Anywhere > Web Services and enable only the sub-features this connector's actions need.

read/get (Read Data) — required for all read actions.
post/insert and patch/update — required to create and update: employees, addresses, contacts, emergency contacts, employment statuses, work assignments, departments, org units, positions, jobs, punches, time off, and schedules.
delete — required only for deleting punches.

On the Authorizations tab, select only the authorizations the integration needs. Each entity offers four rights — always include Can Read alongside any write right.

Can Read — read the entities below.
Can Create / Can Update / Can Delete — add for the entities you write to.
Entities: Employee Contact Information (Business + Personal), Employee Key Information, Employee Personal Information, Employee Financial / Pay Information, Employee Status Information, Employee Work Assignment (Primary + Secondary), Employee Properties (custom fields), and User Information.

On the Web Services Field-Level Access tab, configure which fields are returned for read calls. Expand RESTful Services > Human Resources > Employee. Enable only the fields the integration needs — enabling every field is a security risk. To select a group, click the entity name (not its checkbox), then Select All.

Enable XRefCode (required to return the employee identifier).
Select the field groups this connector uses: Employee managers, Employment Statuses, EmployeeWorkAssignment, EmployeeCompensation, Contacts, Addresses, EmergencyContacts, Locations, and OrgUnitInfos — including their EffectiveStart and EffectiveEnd fields.
Enable Configuration > Location (used by Departments, OrgUnits, Positions, and Jobs).
Enable Workforce Management > EmployeeTimeAwayFromWork (Time Off), EmployeePunches, and EmployeeSchedules.
Enable EmployeePropertyValue (custom fields).

Go to System Admin > User and create a new account. On the Properties tab, create and enable the account, then attach the role you built.

User Name: a unique name (avoid spaces and special characters) — enter the same value in the connector Username field.
Ensure the account is active/enabled.
Set a Password that conforms to the role's password policy, then enter it in the connector Password field and store it securely.
Assign the Web Services role and make it the user's default role — Dayforce evaluates features, authorizations, and field-level access against the default role.

On the user's Location Access tab, give access to only the locations (employee population) the integration needs. Avoid granting whole-organization access when a subset is enough.

Add the location(s) covering the employees the integration must access, and check Primary.
Set a Start Date (Dayforce recommends `1/1/1950`).

Get your Host and Client Namespace

These two values identify your Dayforce tenant. A Dayforce API URL is built as `://////` — for example `https://test.dayforcehcm.com/Api/CompanyName/V1/Employees`.

The Client Namespace (your CompanyId) identifies your Dayforce tenant.

Go to Company > Settings > General and copy the Client Namespace value.
It also appears in your API URL — example: in `https://usconfig261.dayforcehcm.com/Api/acmecorp/V1/...` the namespace is `acmecorp`.

Your host is the subdomain only — the connector appends `.dayforcehcm.com` automatically, so do not include it. Because Dayforce assigns each tenant to a specific data center, confirm the exact host rather than guessing.

Open `https://www.dayforcehcm.com/Api/{clientNamespace}/V1/ClientMetadata` in a browser (replace `{clientNamespace}` with your namespace). The returned `ServiceUri` contains your tenant's real base URL.
Take the subdomain before `.dayforcehcm.com` from that `ServiceUri`.
Example: if your `ServiceUri` is `https://ustest261-services.dayforcehcm.com/...`, your host is `ustest261-services`.

Optional: Get Sample credentials for testing

To try the connector without a live tenant, use the shared Sample credentials from the Dayforce Developer Portal instead of your own tenant. Only the Sample environment provides shared credentials — every other environment requires the Web Services user above.

Sign in to the Dayforce Developer Network, then select your account name in the top-right corner and choose Edit Your Profile.

On the Edit Your Profile page, ensure the environment is set to Sample.

If the Environment is already set to Sample, no changes are needed — skip to the next step.
Otherwise, open the Environment dropdown, choose Sample, and click Save.

Developer Portal Environment dropdown with Sample selected

In the left-hand navigation, expand API Explorer > Employee and open GET Employees.

API Explorer side navigation expanded to API Explorer > Employee > GET Employees

On the GET Employees page, find the Sample environment call parameters box, which lists the shared Web Services credentials. These are both your connector Username and Password and the credentials you enter in the next steps.

Copy the Username and Password listed in the box (they work only in the Sample environment).
You will enter these in StackOne Hub's Username and Password fields when linking your Dayforce account.

API Explorer showing the sample Web Services username and password

Expand the GET method, then click Try it out to enable the request form.

GET Employees request with the Try it out button highlighted

Click Execute to send the request.

GET Employees request with the Execute button and Responses

The first time you execute a request — if you are not already authenticated — your browser shows a Sign in popup. Enter the sample Username and Password from the call parameters box and click Sign in.

After the request runs, read the Sample Host and Client Namespace from the Request URL under Responses (they are also shown on the Developer Network Home page). Dayforce API URLs follow the format `https://host/Api//V1/...`, so both values can be read directly from the Request URL.

Host: the subdomain before `.dayforcehcm.com` in the URL (e.g. `ustest261-services`). The subdomain rotates, so read it from the URL rather than hardcoding it.
Client Namespace: the path segment after `/Api/` (`ddn` for Sample).
You will enter these in StackOne Hub's Host and Client Namespace fields when linking your Dayforce account.

API Explorer request URL showing the sample host and ddn client namespace