One API for every HRIS System
Workday
ADP
BambooHR
Rippling
Gusto
Personio
Greenhouse
UKG
50+ HRIS platforms
Workday
ADP
BambooHR
Rippling
Gusto
Personio
Greenhouse
UKG
50+ HRIS platforms
HRIS APIs are a nightmare. You still have to ship by Friday.
Most HRIS platforms don't have a real API
Employee data lives behind Workday's proprietary SOAP endpoints, BambooHR's limited v1 API, or worse — an export button that emails you a CSV.
Every system has a different data model
One platform calls it employeeId. Another uses workerId. A third buries it three levels deep in a nested XML payload. You write the same mapping logic over and over.
HRIS integrations are a maintenance trap
Platforms push silent schema changes. Auth tokens expire without warning. A new module ships and your sync breaks in production — on the day of a big hire.
Access Any HRIS. Without Writing a Custom Integration.
Works Across Every System
Workday, ADP, BambooHR, Rippling, Gusto, Personio — if your HR team logs in, Deck can reach it. No native API required.
Auth Handled End to End
SSO, OAuth, session tokens, MFA — Deck handles the full authentication layer so you never have to reverse-engineer a login flow again.
Zero Maintenance
When a vendor updates their UI or rotates their token format, Deck adapts. Your integration keeps running. You keep sleeping.
{
"source": "workday",
"employees": [
{
"id": "E-1042",
"name": "Jordan Kim",
"department": "Engineering",
"startDate": "2024-03-15",
"manager": "Sarah Lin"
}
]
}
Five Lines of Code. That's It.
Describe what you need
Tell Deck which HRIS you're connecting to and what data you want — employees, departments, job levels, compensation bands.
Deck handles the rest
Auth, navigation, extraction, normalization. Deck figures out how to get the data and returns it in a consistent schema regardless of source.
Get clean, structured data
Every response is normalized JSON. No more writing field mappers for every platform.
import { Deck } from "@deck-co/sdk"; const deck = new Deck({ apiKey: process.env.DECK_API_KEY }); const employees = await deck.hris.getEmployees({ source: "workday", fields: ["id", "name", "department", "startDate", "manager"], }); console.log(employees.data); // [{ id: "E-1042", name: "Jordan Kim", department: "Engineering", ... }]
What HR and ops teams are pulling with Deck
What teams ask before they build with Deck
Yes. Deck handles SSO, OAuth 2.0, MFA, and session-based auth. If your HR team can log in, Deck can too.
Workday's API is powerful but complex — SOAP-based, tenant-specific, and requires a full implementation effort. Deck gives you the same data in a REST call with a normalized schema, in a fraction of the time.
Yes. Deck can read custom fields, modules, and configurations specific to your tenant — not just the standard data model.
Clean, normalized JSON. Deck maps each platform's native schema to a consistent response format so you don't need to write platform-specific parsing logic.
Deck detects and adapts to changes automatically. Your integration doesn't break — and you don't get a 3am page.
Deck is SOC 2 Type II certified. Employee data is processed in transit only and never stored beyond your configured retention window.