<turbo-stream action="update" target="wiki_card"><template>

<h1>Dayforce REST WebService Connection Setup</h1>
<div class="trix-content"><h3>Overview</h3><p>A Dayforce connection is set up in Rapidi as a <strong>REST WebService</strong>, 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.</p><h3>Authentication: Token Request</h3><p>Unlike a simple Basic Auth setup, Dayforce uses a <strong>token request flow</strong>:</p><ol><li>Rapidi authenticates against a dedicated <strong>Domain</strong> (token endpoint) using the configured Account, User ID, and Password.</li><li>Dayforce returns an access token.</li><li>Rapidi uses that token to call the actual <strong>Server Connect</strong> endpoint for the object being synced (e.g. <code>Employees</code>, <code>EmployeePayAdjustments</code>, <code>LaborMetrics</code>).</li></ol><h3>Example Configuration (<code>REST001</code>)</h3><p></p><figure class="attachment attachment--content"><table class="table table-bordered"><thead><tr><td>Setting</td><td>Value</td></tr></thead><tbody><tr><td>Code</td><td>REST001</td></tr><tr><td>Description</td><td>REST001</td></tr><tr><td>Authentication Type</td><td>Token request (using userid + password)</td></tr><tr><td>Server Connect</td><td>https://can252.dayforcehcm.com/Api/nmb/v1/Employees</td></tr><tr><td>Account</td><td>nmb</td></tr><tr><td>User ID</td><td>nmb_WebService</td></tr><tr><td>Password</td><td>Stored securely</td></tr><tr><td>Domain</td><td>https://dfid.dayforcehcm.com/connect/token</td></tr><tr><td>Metadata URL</td><td>https://myrapidi.github.io/jsonschemas/Dayforce_full_schema_rapidi.json</td></tr><tr><td>Use SSL</td><td>Yes</td></tr></tbody></table><figcaption class="attachment__caption"></figcaption></figure><p></p><h3>Field notes</h3><ul><li><strong>Account</strong> is the Dayforce client namespace (<code>nmb</code> in this example), and appears both in the Server Connect path and as the account identifier used for the token request.</li><li><strong>Server Connect</strong> follows the pattern <code>https://{environment}.dayforcehcm.com/Api/{client_namespace}/v1/{Endpoint}</code>.&nbsp;</li><li><strong>Domain</strong> 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.</li><li><strong>Metadata URL</strong> points to the hosted JSON schema, the single source of truth for what objects and fields are available to map for this connection.</li></ul><h3>Setting Up a New Endpoint</h3><p>Adding a new Dayforce object to the integration is a schema-only change:</p><ol><li>Add the new endpoint's definition to the hosted JSON schema.</li><li>Click <strong>Read Design</strong> on the existing WebService in Rapidi.</li></ol><p>That's it, no new WebService, no changes to Server Connect, Domain, Account, or the other connection fields.</p><p><br></p></div>
</template></turbo-stream>

