SAP SuccessFactors API

Integrate SAP SuccessFactors with your product—along with any other
ATS
HR & Payroll
 application

Connect your product to all the applications your customers use via Merge's

ATS

 

HR & Payroll

 

Unified API to close more deals, retain customers, and expand to new markets

Get a demo
Your Product
Merge
Your customers' data
Activities
Applications
Async Passthroughs
Async Passthroughs
Attachments
Audit Trails
Audit Trails
Bank Info
Benefits
Candidates
Companies
Departments
Dependents

Top integration use cases for SAP SuccessFactors

Read more

Sync SAP SuccessFactors Data

Activities

The Activity object is used to represent an activity for a candidate performed by a user.

Docs
Applications

The Application Object is used to represent a candidate's journey through a particular Job's recruiting process. If a Candidate applies for multiple Jobs, there will be a separate Application for each Job if the third-party integration allows it.

Docs
Attachments

The Attachment object is used to represent a file attached to a candidate.

Docs
Candidates

The Candidate object is used to represent profile information about a given Candidate. Because it is specific to a Candidate, this information stays constant across applications.

Docs
Departments

The Department object is used to represent a department within a company.

Docs
Eeocs

The EEOC object is used to represent the Equal Employment Opportunity Commission information for a candidate (race, gender, veteran status, disability status).

Docs
Jobs

The Job object can be used to track any jobs that are currently or will be open/closed for applications.

Docs
Job Interview Stages

The JobInterviewStage object is used to represent a particular recruiting stage for an Application. A given Application typically has the JobInterviewStage object represented in the current_stage field.

Docs
Job Postings

The JobPosting object represents an external announcement on a job board created by an organization to attract qualified candidates to apply for a specific Job opening

Docs
Offers

The Offer object is used to represent an offer for a candidate's application specific to a job.

Docs
Offices

The Office object is used to represent an office within a company. A given Job has the Office ID in its offices field.

Docs
Users

The RemoteUser object is used to represent a user with a login to the ATS system.

Docs
Interviews

The ScheduledInterview object is used to represent a scheduled interview for a given candidate’s application to a job. An Application can have multiple ScheduledInterviews depending on the particular hiring process.

Docs
Scorecards

The Scorecard object is used to represent an interviewer's candidate recommendation based on a particular interview.

Docs
Screening Questions

The ScreeningQuestion object is used to represent questions asked to screen candidates for a job.

Docs
Tags

The Tag object is used to represent a tag for a candidate.

Docs
Bank Info

The BankInfo object is used to represent the Bank Account information for an Employee.

Docs
Companies

The Company object is used to represent a company within the HRIS / Payroll system.

Docs
Employees

The Employee object is used to represent any person who has been employed by a company.

Docs
Employee Payroll Runs

The EmployeePayrollRun object is used to represent an employee's pay statement for a specific payroll run.

Docs
Employments

The Employment object is used to represent a job position at a company. If an integration supports historical tracking of employments, it will be reflected in the data. If not, a new Employment object will be created whenever there is a change in job title or pay. The effective_date field should be used to order Employment objects, with the most recent date corresponding to the latest employment record for an employee.

Docs
Groups

The Group object is used to represent any subset of employees across, for example, DEPARTMENT or TEAM. Employees can be in multiple Groups.

Docs
Locations

The Location object is used to represent an address that can be associated with an employee.

Docs
Payroll Runs

The PayrollRun object is used to represent a group of pay statements for a specific pay schedule.

Docs
Teams

The Team object is used to represent a subdivision of the company, usually a department. Each employee will be grouped into one specific Team.

Docs
Time Off

The TimeOff object is used to represent all employees' Time Off entries.

Docs
Time Off Balances

The TimeOffBalance object is used to represent current balances for an employee's Time Off plan.

Docs

FAQ on integrating with SAP SuccessFactors’s API

What types of data interactions does Merge support for SAP SuccessFactors?

Merge provides access to various data types in SAP SuccessFactors, including applicants, job postings, candidate information, and more. In addition, you can make POST and GET requests across many of these data types.

Learn more about the endpoints Merge interacts with.

How often does Merge sync data with SAP SuccessFactors?

It depends on the frequency you set (Daily, Standard, High, and Highest) and the Common Model you sync. That said, you may be able to sync data every 5 minutes, 30 minutes, hour, 3 hours, 6 hours, 12 hours, or daily.

Learn more about how often Merge can sync SAP SuccessFactors data.

What organizations use Merge’s SAP SuccessFactors integration?

A wide range of companies use it, including Snappy, BILL, Ramp, and Drata.

You can learn more about the companies that use SAP SuccessFactors and/or other HRIS integrations powered by Merge here.

What features does Merge offer for syncing custom data from SAP SuccessFactors?

Merge supports unique syncing requirements through features like Field Mapping, Remote Data, and Authenticated Passthrough requests.

Here’s more on each feature:

How much does it cost to integrate with SAP SuccessFactors via Merge?

Merge offers Launch, Professional, and Enterprise plans. The Launch plan starts at $650/month for up to 10 linked accounts, with each additional account charged at $65/month. Professional and Enterprise plans provide advanced features and bulk discounts. 

To get exact pricing tailored to your usage, you can contact Merge's team​ of integration experts.

What other HRIS integrations does Merge support?

In addition to SAP SuccessFactors, Merge supports 70+ HRIS integrations, allowing you to access employee data from systems like Workday, BambooHR, ADP Workforce Now, Gusto, UKG Pro, and more. In addition, you can access all of Merge’s HRIS integrations once you’ve built to Merge’s HRIS Unified API—allowing you to scale your HRIS integrations quickly and easily. 

Learn more about the HRIS integrations Merge supports.

Are there any days you’ll be closed for the holidays in 2024?
Trusted to power integrations globally
Build Smarter

Make integrations your competitive advantage

More sales, less code, fewer headaches

Focus on your core product

Stop diverting your engineers to yet another integration and let them get back to work.

Give customer success a break

Manage your simplified integration issues in a single pane. No therapist required.

Stop losing sales due to integrations

Launch integrations in days, not quarters. Your sales team will thank you.

Seamless Account Linking

Integration authentication that feels like magic

Merge seamlessly manages authentication and authorization on behalf of your customers.

Offer account linking and permission controls to your users with Link for a customizable frontend or with Magic Link for URL-based authorization

View docs
APIs Made Simple

The toolkit for all your integration needs

We make integrations painless with accessible API design, dead-simple SDKs, and beautiful documentation that we agonize over.

View docs
Get Employee Data
Python
Ruby
Node
Go
Java
.NET
import merge
from merge.client import Merge
merge_client = Merge(api_key="<YOUR_API_KEY>", account_token="<YOUR_ACCOUNT_TOKEN>")
employee = merge_client.hris.employees.list()

import { MergeClient, Merge } from '@mergeapi/merge-node-client';
const merge = new MergeClient({
  apiKey: 'YOUR_API_KEY',
  accountToken: 'YOUR_ACCOUNT_TOKEN',
});
employee = await merge.hris.employees.list()

ApiClient.instance.authentications.tokenAuth = {
  type: 'bearer',
  accessToken: 'API_KEY',
};
new EmployeesApi().employeesList('ACCOUNT_TOKEN', {}, (data) => {
  console.log(data);
});

import (
  "context"
  "fmt"
  merge "github.com/fern-api/merge-go"
  mergeclient "github.com/fern-api/merge-go/client"
  "github.com/fern-api/merge-go/hris"
)

client := mergeclient.NewClient(
  mergeclient.ClientWithAuthApiKey("<YOUR_API_KEY>"),
  mergeclient.ClientWithHeaderAccountToken("<YOUR_ACCOUNT_TOKEN>"),
)
employee, err := client.Hris().Employees().List(
  context.TODO(),
  &hris.EmployeesRetrieveRequest{
    IncludeRemoteData: merge.Bool(true),
  },
)
if err != nil {
  return err
}
fmt.Printf("Retrieved employee with ID %q\n", *employee.Id)

ApiClient client = Configuration.getDefaultApiClient();
client.setBasePath('https://api.merge.dev/api/ats/v1');
ApiKeyAuth tokenAuth = client.getAuthentication('tokenAuth');
tokenAuth.setApiKey('API_KEY');
CandidatesApi apiInstance = new CandidatesApi(client);
apiInstance.candidatesList('ACCOUNT_TOKEN');

import com.merge.api.MergeApiClient;
import com.merge.api.resources.hris.employees.requests.EmployeesRetrieveRequest;
import com.merge.api.resources.hris.types.Employee;
MergeApiClient mergeClient = MergeApiClient.builder()
    .accountToken("ACCOUNT_TOKEN")
    .apiKey("API_KEY")
    .build();
Employee employee = mergeClient.hris().employees().list(
    EmployeesRetrieveRequest.builder()
        .includeRemoteData(true)
        .build());

{
"id": "0958cbc6-6040-430a-848e-aafacbadf4ae",
"remote_id": "19202938",
"employee_number": "2",
"company": "8d9fd929-436c-4fd4-a48b-0c61f68d6178",
"first_name": "Dirna",
"last_name": "Emanuel",
"display_full_name": "Dirna Emanuel",
"username": "dirnaemanuel",
"groups": [
  "21a54124-397f-494d-985e-3c5b330b8a68"
],
"work_email": "dirna@merge.dev",
"personal_email": "dirnaemanuel@gmail.com",
"mobile_phone_number": "+1234567890",
"employments": [
  "17a54124-287f-494d-965e-3c5b330c9a68"
+ More languages
Meta Endpoint

Programmatically access required schemas

Third-party providers require specific (and often different) fields to write data to their APIs, making your code a mess.

Dynamically fetch required data schemas from Merge’s /meta endpoint to make POST or PATCH requests that just work.

View Docs
Beyond Building

Rely on the best integration observability system

Let our logs, issue detection, and automated alerts save your customer success team time, money, and headaches.

Forget maintenance - let your developers focus on building!

Start for free

How Drata helps thousands streamline their SOC 2 with Merge

Read case study

​​”Working with Merge’s Unified API and beautiful React component took less than a sprint to integrate, test, and release.”

Daniel Marashlian of profile photo
Daniel Marashlian
Co-Founder & CTO

Read more about building and maintaining multiple integrations

A guide to maintaining your product integrations
A guide to maintaining your product integrations
Blog
Blog Posts
10/27/2023
A guide to integrating multiple APIs
A guide to integrating multiple APIs
Blog
Blog Posts
11/13/2023
The top challenges of normalizing multiple API integrations
The top challenges of normalizing multiple API integrations
Blog
Blog Posts
11/20/2023
One Step Ahead

We're the cheat code to your integrations strategy

Revolutionize your integrations strategy for HR, payroll, directory, ATS, project management, ticketing, accounting and CRM platforms.

Start for free or talk to our sales team and learn how Merge makes it easy to add all your integrations in days – not years.
Get a demo
Create free account
ATS
HRIS
ATS
HRIS
Read more