SAP SuccessFactors (platform)

SAP SuccessFactors is the HRIS/HCM system of record - the anchor destination for the permanent-hiring channel. composerID publishes the decision as a Position (Employee Central) and, where Recruiting is live, a Job Requisition, stamps the Intent ID on a custom field, and reconciles the eventual hire (EmpJob) back onto the intent timeline.

API at a glance Minimum viable mapping Custom fields & tenant mapping

Publish path

Direct API

composerID adapter → SAP SuccessFactors API

Events back

Push + poll

events where enabled; poll fallback

API access

Open docs

public developer portal

Contract tier

Tier A

full loop: publish + events back

Tenant configuration (mandatory fields, approval chains, picklists) is a separate gate from vendor capability: it is discovered at preflight before first publish and may need destination admin changes. How composerID connects →

Reference

API at a glance

The public API facts composerID's adapter relies on. Tenant-specific details (custom fields, picklists, approval chains) are confirmed during connection and folded into the MappingProfile.

Authentication	OAuth 2.0 SAML Bearer Assertion - register an OAuth client in Admin Center (Manage OAuth 2.0 Client Applications, X.509 certificate), exchange the signed assertion at POST /oauth/token (grant_type=urn:ietf:params:oauth:grant-type:saml2-bearer, company_id + API key as client_id). HTTP Basic for OData/SFAPI is deprecated and being retired. The API user also needs matching Role-Based Permissions - a token alone is not enough.
API style	OData v2 (primary; $batch for bulk) plus newer OData v4 APIs; REST/JSON
Base URL	https://{api-server}.successfactors.com/odata/v2 (per data center; .eu hosts for EU DCs)
Objects	Position, FOCostCenter, PerPerson, EmpEmployment, EmpJob, User, picklists (Employee Central); JobRequisition, JobApplication, JobOffer, Candidate (Recruiting)
Events / webhooks	Intelligent Services Center events + Integration Center outbound; otherwise delta-query on lastModifiedDateTime.
Rate limits	Tenant-level concurrency/throughput limits (not publicly numeric); 429/503 with backoff; prefer $batch.

Developer access

The SAP SuccessFactors API details are for registered developers

Auth model, base URLs, event posture and rate limits, free with a developer account.

Get free access → Registered developers are recognised automatically.

Readiness

Docs confidence: Public

“Docs confidence” describes how deterministic our mapping templates can be before we connect to a tenant. Even with public docs, implementations vary, especially around custom fields, approval flows and object extensions.

Deterministic mapping

Common Workforce Model fields map to known API fields. Best for standard objects (requisitions, assignments, timesheets, POs).

Tenant discovery

composerID can scan tenant configuration (custom fields, picklists, required fields) where the platform permits it, then generate a tenant‑specific MappingProfile.

Enrichment loop

If the target platform requires a field the Intent record doesn't yet have, composerID emits an enrichment_request back to the intake layer.

Mapping

Minimum viable mapping for SAP SuccessFactors

An opinionated baseline. The platform adapter enforces additional requirements via preflight. “Tenant required” fields are discovered during connection and added to the MappingProfile.

Object	Canonical fields	Platform target	Required status	Notes
Position Create/approve the position to hire against	title, cost_center_id, start_date, location	OData v2 upsert Position (Employee Central)	Required	Position Management anchors the perm decision
Job Requisition Open the requisition in Recruiting	role_title, location, hiring_manager, openings	OData JobRequisition (Recruiting module)	Tenant	Template-driven; Recruiting is separately licensed
Intent ID + hire back-sync Correlate and reconcile	intent_id (cust_ custom field); EmpJob on hire	Custom field + Intelligent Services event	Required	The hire event closes the loop on the intent timeline

Developer access

The field-level mapping is for registered developers

Object targets, canonical fields and the Intent ID carrier for SAP SuccessFactors, free with a developer account.

Get free access → Registered developers are recognised automatically.

Idempotency & drift: publish + reconcileExpand

Publish operations are idempotent using a deterministic key {intent_id}-{intent_version}-{target_system}. Because humans can change records inside the platform, composerID supports reconciliation: it compares the platform record snapshot to the canonical intent and flags drift.

Tenant specifics

Custom fields & unique mapping

Real deployments rely on program-specific custom fields (for compliance, approvals, GL coding, rate rules or supplier constraints). composerID is designed to generate tenant‑specific mappings rather than forcing you to redesign your intake.

How scanning works

High-level flow

connect_destination() → read required fields + picklists (where permitted) → detect custom fields / extensions → build MappingProfile + validation rules → preflight intent against tenant requirements

What gets produced

Portable artefacts

MappingProfile (tenant-scoped) Capabilities matrix Required-field rules Picklist dictionaries Enrichment prompts Audit spine links (defence_file_ref)

Important: where this platform is tenant-definedExpand

SuccessFactors is heavily tenant-configured: MDF objects, picklists and requisition templates differ per tenant, so mapping needs each tenant's schema. API servers are per data center; the OAuth client is registered per instance and the API user must hold matching Role-Based Permissions. Recruiting (JobRequisition) is a separately licensed module - confirm before planning the requisition step.

Developer access

Tenant-mapping notes are for registered developers

Where SAP SuccessFactors deployments differ tenant to tenant, and what to check before first publish.

Get free access → Registered developers are recognised automatically.

Implement the adapter

Use this page alongside the API + Schemas docs to implement: destination connection, preflight validation, publish, webhook back-sync and reconciliation.

Back to Platforms How integrations work API reference