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

<h1>Workday REST WebService Connection Setup</h1>
<div class="trix-content"><div>Connecting to Workday is done through a standard REST WebService: a base URL, an authentication method, and a metadata URL pointing to the schema that describes the data. This is the same generic REST connection type used for other REST-based integrations, not something Workday-specific.<br><br></div><h3><strong>REST WebService Connection Configuration</strong></h3><div><figure class="attachment attachment--content"><table class="table table-bordered"><thead><tr><td>Code</td><td>Internal identifier for the web service</td></tr></thead><tbody><tr><td>Description</td><td>Human-readable label for what this connection is for</td></tr><tr><td>Authentication Type</td><td>Typically Basic auth (user ID + password) using a Workday integration user</td></tr><tr><td>Server Connect</td><td>Base URL of the Workday endpoint being called</td></tr><tr><td>User ID</td><td>Workday integration service account</td></tr><tr><td>Password</td><td>Credential for the integration user, stored securely</td></tr><tr><td>Metadata URL</td><td>Optional link to a JSON schema describing the objects and fields returned by this endpoint</td></tr><tr><td>Use SSL</td><td>Should always be enabled</td></tr></tbody></table><figcaption class="attachment__caption"></figcaption></figure></div><h3><strong>What the endpoint points to:</strong></h3><div>The Server Connect URL can point at any Workday REST endpoint the customer wants to expose, not just a report. Workday reports (RaaS) are one common example, since they're easy for a customer to build and adjust themselves, but the same REST WebService setup works equally well against other Workday tables and endpoints. What changes from case to case is just the URL and, if used, the schema behind the Metadata URL; the connection setup itself stays the same.<br><br></div><h3><strong>What lives on the Workday side vs. the Rapidi side</strong></h3><ul><li><strong>Workday side:</strong> the customer configures and maintains whatever Workday object (report, table, or other endpoint) is being exposed, including its security and access.</li><li><strong>Rapidi side:</strong> the REST WebService just needs the correct URL, credentials, and a Metadata URL pointing to the schema ( built by Rapidi). See <strong>Schema Structure &amp; Field Management</strong> for how that schema is built and kept up to date.</li></ul><h3><strong>Prerequisites</strong></h3><ul><li>A Workday integration system user with access to the endpoint(s) being connected to.</li><li>The endpoint reachable over HTTPS from Rapidi.</li><li>Schema: a hosted, reachable JSON file describing the endpoint's objects and fields.</li></ul><div><br></div></div>
</template></turbo-stream>

