SuccessFactors Integration CPI Basic Guide
SuccessFactors Integration CPI Basic Guide
Currently SuccessFactors supports SFAPI ( Compound Employee ) and OData APIs for integration.Compound
Employee will be used when you are building Integrations around Employee Master data and for rest of the
scenarios we can leverage OData APIs.
Login into SuccessFactors and search for API where you can see multiple options ,will discuss briefly on each one
of those.
API Center:
API Center is centralized reference point for all the configurations related to API.Will cover every option of this API
Center in detail.
OData IP Whitelisting:
This option can be used for restricting access to OData APIs from outside SFSF.
http://<hostname>/odata/v2/User?apiOptionProfileID=<profile ID>
This option gives flexibility to Refresh And Export Metadata from SuccessFactors system.
Whenever custom MDF objects are created or modified its mandatory to perform Metadata refresh to make sure
changes are reflected to your APIs.
Also you have option to download metadata (edmx) file manually to consume this in 3rd party systems.
This option would be helpful while performing insert or upsert operation to SuccessFactors to see the request /
response payload for logging.
You can set the logging for both OData and SFAPI APIs.By default payloads will not be logged and by manually
selecting Enable All Payloads will enable payloads of request and response ( which can be seen in audit log which
would be showcased further in the blog ).
Using this option you would be able to see Request/Response headers and Payalods.Payload wiould be visible only
if you follow previous step and enabled logging by clicking “Enable All Payload”.It Also provides various filtering
options to drill down into request you are looking for.
OData API Data Dictionary:
This is the goto place for get list of APIs,Field Details , Different Type of field and what are operations you can
perform on those APIs.
1: Entity
Entities are instances of entity types.Entity types are named structured types with a key. They define the named
properties and relationships of an entity. Entity types may derive by single inheritance from other entity types.
Below is example of Entity: ToDo which is referring internally Complex Type: ToDoBean
2: Complex Type
Complex types are keyless named structured types consisting of a set of properties. These are value types whose
instances cannot be referenced outside of their containing entity. Complex types are commonly used as property
values in an entity or as parameters to operations.
Complex Types cannot be called directly from outside it can be referenced inside an Entity or it can be set as return
type in Function Import
3: Function Import
For each function import we can define return kind.Three return kinds supported are Complex type,Entity type and
No return.
Below is example of Function Import Of type GET which is returning Complex Type:
4: Supported Operations
There are different set of fields either having primitive types like String,Integer,Boolean or having Complex Type or
referring all together an Entity ( Ex: User Entity Navigation to Matrix Manager ).
6: Associations
Associations are nothing but referring entity from parent Entity.These values can be retrieved using OData query
parameter $expand.
7: Picklist References
Fields referring to Picklists. Picklists are, simply, selection lists used to populate a data input field with one of a
number of predefined values. They act in the same way as F4 Helps in SAP HCM.These values can be maintained
in Picklist Center.
This option can be used when you are using Compound Employee API.This gives complete details of
request/response headers and payloads.
When you click on SFAPI whitelisting it automatically redirects you into “Password and Login Policy Settings – Set
API Login Exceptions…” where you can specify Internet Protocol (IP) address from which the API is accessible.