sdworx-webservice · v1.0.0 · 2026-04-19 · sha256 efbda08531a7a8d4
sdworx-webservice v1.0.0A
Immutable. This exact content never changes and is served at /api/v1/blob/efbda08531a7a8d4.
---
name: sdworx-webservice
description: |
SD Worx (Web service) integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in SD Worx (Web service). Routes through Apideck with serviceId "sdworx-webservice".
license: Apache-2.0
alwaysApply: false
metadata:
author: apideck
version: "1.0.0"
serviceId: sdworx-webservice
unifiedApis: ["hris"]
authType: basic
tier: "2"
verified: true
status: beta
---
# SD Worx (Web service) (via Apideck)
Access SD Worx (Web service) through Apideck's **HRIS** unified API — one of 58 HRIS connectors that share the same method surface. Code you write here ports to BambooHR, Deel, Hibob and 54 other HRIS connectors by changing a single `serviceId` string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant SD Worx (Web service) plumbing.
> **Beta connector.** SD Worx (Web service) is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.
## Quick facts
- **Apideck serviceId:** `sdworx-webservice`
- **Unified API:** HRIS
- **Auth type:** basic
- **Status:** beta
- **SD Worx (Web service) docs:** https://www.sdworx.com
- **Homepage:** https://www.sdworx.com/
## When to use this skill
Activate this skill when the user explicitly wants to work with **SD Worx (Web service)** — for example, "sync employees in SD Worx (Web service)" or "list time-off requests in SD Worx (Web service)". This skill teaches the agent:
1. Which Apideck unified API covers SD Worx (Web service) (HRIS)
2. The correct `serviceId` to pass on every call (`sdworx-webservice`)
3. SD Worx (Web service)-specific auth and coverage caveats
For the full method surface (parameters, pagination, filtering), use your language SDK skill:
- [`apideck-node`](../../skills/apideck-node/), [`apideck-python`](../../skills/apideck-python/), [`apideck-dotnet`](../../skills/apideck-dotnet/), [`apideck-java`](../../skills/apideck-java/), [`apideck-go`](../../skills/apideck-go/), [`apideck-php`](../../skills/apideck-php/), or [`apideck-rest`](../../skills/apideck-rest/)
For the raw OpenAPI spec:
- **HRIS:** [https://specs.apideck.com/hris.yml](https://specs.apideck.com/hris.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=hris)
## Minimal example (TypeScript)
```typescript
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List employees in SD Worx (Web service)
const { data } = await apideck.hris.employees.list({
serviceId: "sdworx-webservice",
});
```
## Portable across 58 HRIS connectors
The Apideck **HRIS** unified API exposes the same methods for every connector in its catalog. Switching from SD Worx (Web service) to another HRIS connector is a one-string change — no rewrite, no new SDK.
```typescript
// Today — SD Worx (Web service)
await apideck.hris.employees.list({ serviceId: "sdworx-webservice" });
// Tomorrow — same code, different connector
await apideck.hris.employees.list({ serviceId: "bamboohr" });
await apideck.hris.employees.list({ serviceId: "deel" });
```
This is the compounding advantage of using Apideck over integrating SD Worx (Web service) directly: code against the unified HRIS API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
## Authentication
- **Type:** Basic auth (username/password)
- **Managed by:** Apideck Vault — credentials are collected through the Vault modal and stored encrypted server-side.
- **Note:** basic auth connectors often require manual rotation by the end user. If auth fails persistently, prompt them to re-enter credentials in Vault.
See [`apideck-best-practices`](../../skills/apideck-best-practices/) for Vault setup, connection lifecycle, and handling re-auth flows.
## Verifying coverage
Not every HRIS operation is supported by every connector. Always verify before assuming a method works:
```bash
curl 'https://unify.apideck.com/connector/connectors/sdworx-webservice' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}"
```
See [`apideck-connector-coverage`](../../skills/apideck-connector-coverage/) for patterns around `UnsupportedOperationError` and connector-specific fallbacks.
## Escape hatch: Proxy API
When an endpoint isn't covered by the HRIS unified API, use Apideck's Proxy to call SD Worx (Web service) directly — Apideck injects auth headers and handles token refresh. Set `x-apideck-downstream-url` to the target endpoint on SD Worx (Web service)'s own API:
```bash
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: sdworx-webservice" \
-H "x-apideck-downstream-url: <target endpoint on SD Worx (Web service)>" \
-H "x-apideck-downstream-method: GET"
```
See [SD Worx (Web service)'s API docs](https://www.sdworx.com) for available endpoints.
## Sibling connectors
Other **HRIS** connectors that share this unified API surface (same method signatures, just change `serviceId`):
[`bamboohr`](../bamboohr/), [`deel`](../deel/) *(beta)*, [`hibob`](../hibob/), [`personio`](../personio/), [`workday`](../workday/), [`adp-ihcm`](../adp-ihcm/) *(beta)*, [`adp-workforce-now`](../adp-workforce-now/) *(beta)*, [`paychex`](../paychex/) *(beta)*, and 49 more.
## See also
- [HRIS OpenAPI spec](https://specs.apideck.com/hris.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=hris)
- [`apideck-connector-coverage`](../../skills/apideck-connector-coverage/) — programmatic coverage checks
- [`apideck-best-practices`](../../skills/apideck-best-practices/) — architecture, Vault, pagination, error handling
- [`apideck-node`](../../skills/apideck-node/) — TypeScript / Node SDK patterns
- [SD Worx (Web service) official docs](https://www.sdworx.com)