Dayforce REST WebService Connection Setup

Overview

A Dayforce connection is set up in Rapidi as a REST WebService, using token-based authentication against Dayforce's API. One WebService is configured per Dayforce endpoint (Employees, EmployeePayAdjustments, LaborMetrics, etc.), all sharing the same authentication pattern and metadata schema.

Authentication: Token Request

Unlike a simple Basic Auth setup, Dayforce uses a token request flow:

1. Rapidi authenticates against a dedicated Domain (token endpoint) using the configured Account, User ID, and Password.
2. Dayforce returns an access token.
3. Rapidi uses that token to call the actual Server Connect endpoint for the object being synced (e.g. Employees, EmployeePayAdjustments, LaborMetrics).

Example Configuration (REST001)

Field notes

• Account is the Dayforce client namespace (nmb in this example), and appears both in the Server Connect path and as the account identifier used for the token request.
• Server Connect follows the pattern https://{environment}.dayforcehcm.com/Api/{client_namespace}/v1/{Endpoint}. 
• Domain is Dayforce's OAuth-style token endpoint, common across environments for the tenant, and is what actually receives the Account/User ID/Password to obtain the access token.
• Metadata URL points to the hosted JSON schema, the single source of truth for what objects and fields are available to map for this connection.

Setting Up a New Endpoint

Adding a new Dayforce object to the integration is a schema-only change:

1. Add the new endpoint's definition to the hosted JSON schema.
2. Click Read Design on the existing WebService in Rapidi.

That's it, no new WebService, no changes to Server Connect, Domain, Account, or the other connection fields.