v1.0.0 to v1.0.0

4 added, 0 removed. Audit A to A.

---

name: sap-successfactors

description: |

SAP SuccessFactors integration via Apideck's HRIS, ATS unified API — same methods work across every connector in HRIS, ATS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in SAP SuccessFactors. Routes through Apideck with serviceId "sap-successfactors".

license: Apache-2.0

alwaysApply: false

metadata:

author: apideck

version: "1.0.0"

serviceId: sap-successfactors

unifiedApis: ["hris", "ats"]

authType: oauth2

tier: "2"

verified: true

---

# SAP SuccessFactors (via Apideck)

Access SAP SuccessFactors through Apideck's **HRIS, ATS** 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 SAP SuccessFactors plumbing.

## Quick facts

- **Apideck serviceId:** `sap-successfactors`

- **Unified APIs:** HRIS, ATS

- **Auth type:** oauth2

+ - **Apideck setup guide:** [Connection guide](https://developers.apideck.com/connectors/sap-successfactors/docs/consumer+connection)

- **SAP SuccessFactors docs:** https://help.sap.com/docs/SAP_SUCCESSFACTORS_PLATFORM

- **Homepage:** https://successfactors.com

## When to use this skill

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

1. Which Apideck unified API covers SAP SuccessFactors (HRIS, ATS)

2. The correct `serviceId` to pass on every call (`sap-successfactors`)

3. SAP SuccessFactors-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)

- **ATS:** [https://specs.apideck.com/ats.yml](https://specs.apideck.com/ats.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=ats)

## 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 SAP SuccessFactors

const { data } = await apideck.hris.employees.list({

serviceId: "sap-successfactors",

});

```

## Portable across 58 HRIS connectors

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

```typescript

// Today — SAP SuccessFactors

await apideck.hris.employees.list({ serviceId: "sap-successfactors" });

// 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 SAP SuccessFactors 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:** OAuth 2.0

- **Managed by:** Apideck Vault — Apideck handles the full OAuth dance (authorization code flow, token exchange, refresh). Never ask the user for API keys or tokens directly.

- **User setup:** Users authorize via the Vault modal. Connection state progresses `available → added → authorized → callable`.

- **Token refresh:** automatic. Expired tokens are refreshed transparently on the next API call.

+ **Setup guide:** Apideck publishes a step-by-step guide for registering an OAuth app / configuring credentials for SAP SuccessFactors — see [https://developers.apideck.com/connectors/sap-successfactors/docs/consumer+connection](https://developers.apideck.com/connectors/sap-successfactors/docs/consumer+connection). Use that as the authoritative source when walking users through connection setup.

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/sap-successfactors' \

-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 SAP SuccessFactors directly — Apideck injects auth headers and handles token refresh. Set `x-apideck-downstream-url` to the target endpoint on SAP SuccessFactors'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: sap-successfactors" \

-H "x-apideck-downstream-url: <target endpoint on SAP SuccessFactors>" \

-H "x-apideck-downstream-method: GET"

```

See [SAP SuccessFactors's API docs](https://help.sap.com/docs/SAP_SUCCESSFACTORS_PLATFORM) for available endpoints.

## Sibling connectors

Other **HRIS** connectors that share this unified API surface (same method signatures, just change `serviceId`):

[`bamboohr`](../bamboohr/), [`workday`](../workday/), [`deel`](../deel/) *(beta)*, [`hibob`](../hibob/), [`personio`](../personio/), [`adp-ihcm`](../adp-ihcm/) *(beta)*, [`adp-workforce-now`](../adp-workforce-now/) *(beta)*, [`paychex`](../paychex/) *(beta)*, and 49 more.

Other **ATS** connectors that share this unified API surface (same method signatures, just change `serviceId`):

[`greenhouse`](../greenhouse/), [`workday`](../workday/), [`lever`](../lever/), [`workable`](../workable/) *(beta)*, [`bullhorn-ats`](../bullhorn-ats/) *(beta)*, [`teamtailor`](../teamtailor/) *(beta)*, [`freshteam`](../freshteam/), [`jobadder`](../jobadder/) *(beta)*, and 2 more.

## See also

+ - [Apideck connection guide for SAP SuccessFactors](https://developers.apideck.com/connectors/sap-successfactors/docs/consumer+connection)

- [HRIS OpenAPI spec](https://specs.apideck.com/hris.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=hris)

- [ATS OpenAPI spec](https://specs.apideck.com/ats.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=ats)

- [`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

- [SAP SuccessFactors official docs](https://help.sap.com/docs/SAP_SUCCESSFACTORS_PLATFORM)