sdworx-webservice
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, Workday, Deel 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:
- Which Apideck unified API covers SD Worx (Web service) (HRIS)
- The correct
serviceIdto pass on every call (sdworx-webservice) - SD Worx (Web service)-specific auth and coverage caveats
For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node,apideck-python,apideck-dotnet,apideck-java,apideck-go,apideck-php, orapideck-rest
For the raw OpenAPI spec:
Minimal example (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.
// 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: "workday" });
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 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:
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 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:
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 for available endpoints.
Sibling connectors
Other HRIS connectors that share this unified API surface (same method signatures, just change serviceId):
bamboohr, workday, deel (beta), hibob, personio, adp-ihcm (beta), adp-workforce-now (beta), paychex (beta), and 49 more.
See also
- HRIS OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- SD Worx (Web service) official docs
More from apideck-libraries/api-skills
apideck-connector-coverage
Check Apideck connector API coverage before building integrations. Use when determining which operations a connector supports, comparing connector capabilities, or diagnosing why an API call fails with a specific connector. Teaches agents to query the Connector API for real-time coverage data.
18apideck-rest
Apideck Unified REST API reference for any language. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of Apideck's 200+ connectors using direct HTTP calls. Covers authentication headers, CRUD operations, cursor-based pagination, filtering, sorting, error handling, rate limiting, pass-through parameters, and webhooks. Language-agnostic — works with curl, fetch, axios, httpx, or any HTTP client.
16sharepoint
|
4sage-business-cloud-accounting
|
4shopify
|
3odoo
|
3