justworks

name: justworks description: | Justworks 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 Justworks. Routes through Apideck with serviceId "justworks". license: Apache-2.0 alwaysApply: false metadata: author: apideck version: "1.0.0" serviceId: justworks unifiedApis: ["hris"] authType: none tier: "2" verified: true

Justworks (via Apideck)

Access Justworks 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 Justworks plumbing.

Quick facts

Apideck serviceId: justworks
Unified API: HRIS
Auth type: none
Gotchas: page
Homepage: https://justworks.com/

When to use this skill

Activate this skill when the user explicitly wants to work with Justworks — for example, "sync employees in Justworks" or "list time-off requests in Justworks". This skill teaches the agent:

Which Apideck unified API covers Justworks (HRIS)
The correct serviceId to pass on every call (justworks)
Justworks-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, or apideck-rest

For the raw OpenAPI spec:

HRIS: https://specs.apideck.com/hris.yml · API Explorer

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 Justworks
const { data } = await apideck.hris.employees.list({
  serviceId: "justworks",
});

Portable across 58 HRIS connectors

The Apideck HRIS unified API exposes the same methods for every connector in its catalog. Switching from Justworks to another HRIS connector is a one-string change — no rewrite, no new SDK.

// Today — Justworks
await apideck.hris.employees.list({ serviceId: "justworks" });

// 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 Justworks 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: custom (connector-specific)
Managed by: Apideck Vault — setup may involve extra fields beyond a single token. The Vault modal will prompt for everything required.
Refer to: the Apideck dashboard or apideck-best-practices for auth troubleshooting.

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/justworks' \
  -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 Justworks directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Justworks'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: justworks" \
  -H "x-apideck-downstream-url: <target endpoint on Justworks>" \
  -H "x-apideck-downstream-method: GET"

See Justworks'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.