SFAPI is SuccessFactors web-service to import or export data to or from SuccessFactors. 47. The project was a side-by-side SuccessFactors extension. Tenant URL – Enter the name of the SuccessFactors OData API services endpoint. Symptom. . Setting the Passwords for the API User IDs created above. In short: it is not possible to combine two 'lastModifiedDateTime' filters to represent a time interval. Properties and Navigation Properties. 2 (Import Employee via SFSF Application UI) Section 5*: Setting the Password for the API User. 0. 2251702. Search for additional results. Assigned Tags. Step 1: Create an app variable. Creating User IDs via Option 1 (Provisioning) 14. Any resemblance to real data is purely coincidental. There are three main steps in this wizard: Connect to System: In this step, you provide the details required for connecting to the Web Service that you’re accessing. Resolution. Tenant URL – Enter the name of the SuccessFactors OData API services endpoint. Objective: We would like to share one video with hands on using SAP SuccessFactors inbound Integrations Center along with custom MDF entities in OData V2 integration. This is expected behavior. In the following example, admin users with OData API job application export permission can initiate assessment during insert operation if assessment is configured for the New/Default Application status. SAP Knowledge Base Article - Public. New and Improved Features in OData V4 Note The following features are supported in the standard OData v4 protocol. You can use SuccessFactors ODATA Connector to connect to SuccessFactors from. 0, including Onboarding 1. To authorize your IP address for OData API access, go to API Center OData API IP Whitelisting. sap entity query-builder odata metadata-extractor api-builder successfactors Updated Sep 14, 2023; C#; dirigiblelabs / successfactors-synchronizer Star 0. Repeat this action until you get all data via API. It has the format: username@companyID. If you are not familiar creating SAP SuccessFactors OData API username, you can follow also the instructions of this guided answers here. Using the search filters Entity, Complex Type, or Function Import also lets you narrow your search by Tag, for example EC - Payment Information . API to access Calibration data such as subject rank, feedback and rating. Learn what OData v4 APIs are available in SAP SuccessFactors HXM Suite. The SuccessFactors activities. The OData API can return a maximum number of 1000 records in a single page. I am trying to get current and future dated records from SuccessFactors for any entity. OData Name. The permissions listed here grant users and administrators access to the SAP SuccessFactors OData API and SFAPI. It has the format: username@companyID. The ODATA API Dictionary does not mirror Ad Hoc Reports. 0 provides a standards-based mechanism for Single Sign-On (SSO). Scenario 1: personIdExternal='akoelemij'sample: /odata/v2/ or /sfapi/v1 endpoints. Some OData services (e. To see more about this process above you can check the OData developer handbook chapter 3. WFS requires data a week before it’s go live to set up the time profiles, and hence, we shall have EC going. Proxy. Entity Relation Diagram. SAP SuccessFactors HXM Suite OData API provides methods for create, read, update and delete operations. 3. This blog explains how you can trigger workflows attached to a MDF object using OData APIs. It covers comprehensive guidelines for picking the right API for different use cases, delta and deletion handling, handling date/time data with API, batching API request, accessing workflow data and. Admin Username – Enter the username of the SuccessFactors API user account, with the company ID appended. If necessary, move the XML file. Run the code generation. You can read data from SuccessFactors or from other applications. Log in to the SuccessFactors system and use the Search feature to search for ‘OData’. In the OData API data dictionary, you can use Search All, or narrow your search to Entity, Complex Type, or Function Import. Step 3:Configure the SuccessFactors OData V2 channel ( you can use SuccessFactors SOAP for Compound Employee API ). The SAP SuccessFactors HXM Suite OData API is a Web Service API feature based on the OData protocol. In our SuccessFactors instance we first create the OAuth2 client. How to check and understand Odata API Audit logs in SuccessFactors System? Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Supported Operations. SAP SuccessFactors solutions are cloud-based HCM software applications that support core HR and payroll, talent management, HR analytics and workforce planning, and. Authentication We’ve just published a new tutorial series covering a very simple end-to-end sidecar extension scenario which you can access here: Building Extensions for SAP SuccessFactors using APIs and Events Playlist. Similar knowledge is applicable for CSV inbound. Data is not deleted, rather it would be date-delimited. Sample. 0 Client API. A global, cloud-based human resource management software system, evolving to help people and businesses thrive in the experience economy. Image/data in this KBA is from SAP internal systems, sample data, or. Get the required Success Factors credentials for your organization instance along with the. g. Any resemblance to real data is purely coincidental. The User entity has field-level permission control. 4) Create your integration flow in Cloud. Error: The metadata document could not be read from the. Image/data in this KBA is from SAP internal systems, sample data, or demo systems. a} or $ {property. The custom MDF has three fields externalCode as AutoNumber, User ID as USER and comments as String. These data types make it easy for integration clients to convert date and time values to different time zones as needed. Hello SAP community, With the 2H 2020 Release of SAP SuccessFactors application, we are announcing the sunset (planned retirement) of HTTP Basic Authentication for API calls (both SFAPI & OData). Use the Common Name (CN): SF and then press “Generate”. The term technical user or non-RBP usually is the same as Admin Mode. Choose Internet. On a recent project we got to use the UI5 v4 ODataModel, which has been under development for some time. Register the service in the SAP SuccessFactors system. So, we arrived at the last and critical part of the scenario, to trigger save rule while updating pay component information via ODATA API call. You are trying to get data from deleted records in an MDF object using the ODATA API in SuccessFactors. Typically, the path is /usr/sap/trans/. You can use the dictionary to look up EntitySets, Complex Types, and Function Imports that are. How ever in order to consume any OData service from the SuccessFactors OData API test system,you will be using your SAP Cloud Platform trial account user id and password. This guide focuses on OData version 2. In OData v4, you can use the PATCH HTTP method to merge records. Through. 16. 0 MDF entities, and Onboarding entities. SAP SuccessFactors Learning all versions. HTTP Basic Authentication (Basic Auth) is an authentication method used to access APIs in SAP SuccessFactors. Use Case 2: Modifying a Picklist Option with Merge. By default OData API User entity won't return data for inactive users unless you explicitly specify in the query statement. 5. Currently SuccessFactors supports SFAPI ( Compound Employee ) and OData APIs for integration. URL of the SuccessFactors data center that you want to connect to. To set up connection between the service and SAP SuccessFactors, you need to set up OAuth Authentication in SAP SuccessFactors. Looping Process Call. 2493579-Employee Central: Person/User IDs Used Within Employee Central - SuccessFactors Employee Profile. 8 In the same permissions box, go to User Permissions -> Employee Data and review the attributes that the service account can read from the. In the following example, we were able to get most of the oData standard information, but we were also interested in getting the “Label” (here below: Address) and the oData “sf. In the next screen, press connect. Connection Details URL : Enter the OData service provider URL of the SAP SuccessFactors service that you want to access. When that limit is exceeded, it uses a mechanism called Pagination, which will make the response return the exceeding records in a subsequent page. In case of SuccessFactors OData -V4 we dont have that luxury. Select Connectivity > Destinations. The first thing you need to do is to get the XML files (EDM XML – Entity Data Model XML – in short EDMX) which define the entities that compose the OData services to be consumed in the application. The refresh may take a few minutes. Configure and use your SAP SuccessFactors solutions to reduce biases and embed diversity, inclusion, and equity directly into your HR processes. userId = User ID used by the registered client in SuccessFactors. SAP Help PortalChanged We updated information on OData API permissions and the Mapping Extension Field topics. Here's a list of API servers and mTLS certificate servers for SAP SuccessFactors data centers. 0 authentication: Use /oauth/idp to pass a private key to generate a signed SAML assertion. OData API. Testing. Enter a meaningful Project Name. This would affect ODATA API request and validate if client Application from where ODATA API call is being triggered is encoding the special character " Space" or not. Suggested reading: OData V2 Refresh Cache On. SuccessFactors OData V2 receiver supportes Upsert with content-type : atom+xml only. 0 is the ability to call the SuccessFactors OData APIs with the so called. SAP SuccessFactors HXM Suite OData API provides methods for create, read, update and delete operations. Use Case 2: Retrieve the Employment Records of All Candidates Created in Onboarding. For more information about OData API configurations, see the SuccessFactors HCM Suite OData API Programmer's Guide Note Currently, location data is fetched via OData API. How artificial intelligence and machine learning can be used throughout the recruiting process. In the Metadata Frameworkcategory select ‘Configure Object Definitions’ and ‘Admin Access to MDF OData API. clientID = API Key from the registered client in SuccessFactors. Features. Both SHA-2 and SHA-1 signing algorithms are supported. 0) and for Access token as “access_token” as followed in the RFC-7522 specification. This KBA will share samples of OData JSON and XML format with inline upserts (parent and child) in the same request payload. 4. Downloads an XML file with the metadata from the cache. Even if it seems to make sense semantically, the API will not interpret it as a range. Overview. cs and Service1. Now let's start doing OData API queries using 4 different scenarios. Click on the under the Main Data Source heading. Using postman everything works fine but, once I check the connection of destination previously created, the response received is 401: Unauthorized. Click more to access the full version on SAP for Me (Login required). 0 bot from CAI chatbot to update SuccessFactors Principal Propagation in SAP Integration Suite from external system to SuccessFactors Using OAuth 2. I will refer to this extension through. For more information, see Configure the. Hello SAP community, If you regularly call the SAP SuccessFactors’ OData API’s for test purposes using your API test tool of choice, chances are that you are already aware that the Basic Authentication is deprecated and must not be used; instead, the authentication using OAuth 2. Type of Change Description More Info13. Symptom. General guidelines about OData v2 APIs in SAP SuccessFactors HXM Suite, including general permissions, authentication, metadata, query and edit operations, as well as how to use the API Center tool to help you get your way around OData APIs. In this guide, you'll learn how to work with OData v4. Hence you can avoid the refresh by disabling metadata refresh. The idea here is, the tasks as part of TodoEntryV2 api shall be fetched which are owned by the logged on user of myTasksApp application. Now we want to sync all the users from SAP SuccessFactors Application to IAS into different groups – segregation will be based on the domain names of the users. Image/data in this KBA is from SAP internal systems, sample data, or demo systems. It essentially creates a hub-and-spoke data distribution system using a standardized subset of employee master data in a. 0. The test steps described in this KBA are to verify if there is any SPACE special character being sent by client application to SuccessFactors. Click Load to establish the connection to your SAP SuccessFactors data from Power BI. This is my example query: GET. This is a collection of the most useful SAP SuccessFactors Employee Central resources: documents, blogs, reports, and videos. SAP SuccessFactors uses the terminology for Authorization token as “Assertion” (SAML2. The Upsert operation is an SAP SuccessFactors function import to update or insert records. Select tables in the Navigator dialog. Connection Details URL : Enter the OData service provider URL of the SAP SuccessFactors service that you want to access. In OData v4, you can use the PATCH HTTP method to merge records. . To celebrate this most recent release, here’s SuccessFactors Onboarding look at some of the most interesting features and changes introduced since last time. The Solution. • Customers currently restricting access of these API endpoints via an IP-based “allow list” will need to transition the allow list to domain-based allow list described later in this document. Attachment is a generic API to upsert any. A very common implementation scenario is when messages are enriched with SuccessFactors ODATA calls with multiple queries in a local integration process which is called by a looping flow step. How to enable the OData API (V2) in SuccessFactors? Image/data in this KBA is from SAP internal systems, sample data, or demo systems. The SAP SuccessFactors ODBC Driver is a powerful tool that allows you to connect with live data from SAP SuccessFactors, directly from any applications that support ODBC connectivity. Click on File -> New SOAP Project. endpoint, URL, WSDL, wizdler, odata, suffix, SFAPI, suffix, port number, mTLS, certificate, ip , KBA , LOD-SF-INT-API , API & Adhoc API Framework , LOD-SF-INT , Integrations , LOD-SF-INT-ODATA , OData API. It is important to understand what is going on here. The project was a side-by-side SuccessFactors extension. This article describes the steps on how to perform ODATA API queries and upsert requests via Postman. This document explains: How to perform a query operation using the Odata API entity? What is the API response in this case? How to retrieve profile Photo from the API response without Provisioning job?. Select the line and click in Process: This will trigger the ERP IDOC (RFC) > CPI (middleware) > SF OData upsert (update the Admin center > Manage Data > Position). Get the required Success Factors credentials for your organization. com as allowed principal and must be available in at least more than 50% AZs in a region. 1 Configuration in SAP SuccessFactors A Technical Communication User is needed to call OData services in SAP SuccessFactorsPass your SAML assertion and API key (in the client_id field) along with other information to generate an OAuth token. This will ensure that when Gem makes queries to the SuccessFactors OData API for certain fields, they will be visible and allow you to report on them. It’s intended to enable access to SAP SuccessFactors data in the system. The Microsoft Entra SuccessFactors connector uses SuccessFactors OData API to retrieve changes and provision users. Related Information. The reason for these errors is due to incorrect request data sent to the SFSF system. It defaults to &asOfDate=<today's date>. SAP SuccessFactors Employee Central is a flexible, global core HR solution that supports core HR processes and employee self-services for your total workforce. Configure People Profile. Prepare configuration on SCP Cloud. Locat Integration Process call to get User data from SuccessFactors. This KB article explains what OData API is and what possibilities it offers when in use with the Recruiting Management Module. SAP SuccessFactors Connector 4. It replicates employee master data from Employee Central to SAP systems, payroll. In the context of a receiver adapter, this header can be used to dynamically change the URI to be called. Use Case 2: Creating a Position with Insert. P. About SAP SuccessFactors OData APIs (V2) Authentication Permissions Metadata Operations MDF OData API API Center Errors, Timeouts, and Access Limits API. Hello SAP Community, With the advent of the 2H 2020 in SAP SuccessFactors, the Entities Job Requisition and Job Offer in OData now support the Position Generic Object, so it is now possible to use both OData API and the UI to create a Job Requisition or Offer with the Position Generic Object. 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. Additional Information. SAP blogs let you read about and share your own technical know-how, industry insights, and the latest buzz about technology, events, and all things SAP. Employee Central consists of employee entities and foundation entities: Employee Entities: Describes person and employment objects. 0 Let’s call iRPA 2. Click on Finish. 1. Learn how to retrieve OData metadata in SAP SuccessFactors HXM Suite. 0) APIs for integration and data replication. Step 1: Upload the transport request files. It's intended to enable access to SAP SuccessFactors data in the system. Use Case 1: Querying a Picklist Option. In the adapter configure all the mandatory parameters. With use of OData API, it provides with built on protocols like HTTP following the REST methodologies for data transfer. Learn how to retrieve OData metadata in SAP SuccessFactors HXM Suite. This adapter exchanges data with a remote component that might be outside the scope of SAP. privateKey = Use the private key you uploaded when you register your client in Successfactors or for this example, we will use the private key we generate from Successfactors. 1. 1. Choose an entity in Odata API Data Dictionary which supports upsert functionality; Create a request payload; Setting the correct request headers, pass the payload to SFSF in a client tool (Middleware/REST client) Cause. This will remove the deduction pay component, and will replicate the ECP accordingly. With enhanced SAP SuccessFactors oData V2 outound connector, it’s possible to configure oAuth SAML Bearer in context of an API user for SAP SuccessFactors system. If you want to use location data, you must configure the OData API. Integrating SAP SuccessFactors Employee Central with Microsoft Active Directory (SAP Cloud Integration)Steps to follow: Pick Personal Information API from SAP Successfactors API Center – OData API Data Dictionary. 1. You may choose to manage your own preferences. Let’s Start – Login to SuccessFactors Portal (I assume you have full access or ability to Proxy as “sfadmin” user) Step 1: OData IP Allowlisting. • The. It is an alternate integration. However, the deleted record is not able to capture from OData API. 1. General guidelines about OData v2 APIs in SAP SuccessFactors HXM Suite, including general permissions, authentication, metadata, query and edit operations, as well as how. In the SAP BTP cockpit, navigate to your extension subaccount in the Cloud Foundry environment. To push this to CPI and SuccessFactors, please use the transaction: Access the transaction BD87 > type the IDOC ID and run. SAP Cloud Integration’s SuccessFactors OData V2 adapter (version 1. Features. Here's a list of API servers and mTLS certificate servers for SAP SuccessFactors data centers. By default, Server-Side Pagination is selected and as per the requirements, you can select the appropriate pagination type. through a. In order to resolve the issue, you need to ensure you pass the REQUEST in correct format. com Content-Type: multipart/mixed; boundary=batch_36522ad7-fc75-4b56-8c71-56071383e77b Before constructing the request body, I would like to explain the use of postman variables in the API request. This site uses cookies and related technologies, as described in our privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. Supported Operations. In the above iflow Successfactors Odata V2 adapter is used. To. Reproducing the Issue. The performance OData APIs has some limitations. In successfactors Odata autdit log, we can see HTTP request like this. Help Portal – List of SAP SuccessFactors API Servers. Logical Operators LOGICAL OPERATORSAP SuccessFactors provides two APIs for its integration with Identity Provisioning: SAP SuccessFactors HCM Suite OData API and SAP SuccessFactors Workforce SCIM API. IAS is setup. Use Case 3: Update External User Record with Employment-Related Information. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. This article describes the process on how one can access SuccessFactors OData APIs from an ABAP program using the OAuth 2. Related Information. SAP SuccessFactors HXM Suite provides a variety of OData APIs for customers to build their extensions and integrations. User Insert, apiOptionProfileID, processInactiveEmployees , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , How ToIt's now 2021 and a properly functioning OData connector in Power BI seems to still be outstanding. For a list of the API Endpoint URL for the SAP SuccessFactors environments, see About HXM Suite OData APIs. In productive scenarios, the metadata seldom changes. Add destinations in HCP for SAP Successfactors & 3 rd party application. Log into your SAP SuccessFactors HXM Suite system. This application allows user to explore SuccessFactors oData API metadata. Proxy Type. It has successfully deleted entry of Position. Click an SAP SuccessFactors connection type tile for your source. Click on Add app variable. Calling SuccessFactors OData APIs via iRPA 2. On a recent project we got to use the UI5 v4 ODataModel, which has been under development for some time. You can use the OData APIs to generate access tokens for OAuth 2. api. Only enter the host name of server. The wizard can also fetch the Externalized parameters that are maintained under the Connection details of the OData receiver adapter. Usually with SuccessFactors OData -V2 we will be able to get the schema once perform model operation. Setup and run a mock server test. You can use the Integration Center to immediately run or schedule a job to export a provider-specific OData object to SFTP, based on defined filter conditions and applying a provider-defined output order and file. If there are network issues, you enable the integration flow to retry connecting to the SuccessFactors OData V2 service. The retry happens for the following operations: Query – for HTTP response codes 502, 503, 504, and 429. Admin Center -> Select the Permission Role -> Click on Permissions Tab. The OData API is a solution with allows to export, create and update. 1 Configuration in SAP SuccessFactors A Technical Communication User is needed to call OData services in SAP SuccessFactors Pass your SAML assertion and API key (in the client_id field) along with other information to generate an OAuth token. Introduction SAP Cloud Integration version 2. This enables Position data to be integrated with any system, so long as the system or middleware supports the OData protocol. Deploy your IFlow to see end to end result. 0. SAP SuccessFactors, ServiceNow, and SAP Integration Suite need to be configured and prepared before the integration content package can be configured and deployed. SAP Help Portal Page Not Found | SAP Help Portal. Enable OData VDM code generation. 2 Create a scope (in this example it is called dummyScope) 5. SAP Knowledge Base Article - Preview. An easy way to get external data to be made available within the Data Warehouse Cloud, is. Insert. Related Information. 2250344 - How to enable OData API (V2) - SuccessFactors | SAP Knowledge Base Article. Consume OData API Video Tutorial. Data can be defined as static JSON or dynamically by making API calls. OData v2 uses HTTP method POST and HTTP header X-HTTP-METHOD: MERGE to merge records. 2800150 – How to test OAuth authentication via Postman. Type of Change Description More Info 13. Use the Position entity to. Complete the configure connection properties. Select Connectivity > Destinations. You can get such files from SAP API Business Hub. For those looking for light-weight connection option with SuccessFactors, OData API is the answer. Example. On your IPS tenant, go to your Source System, then select ‘ Jobs ‘ tile, and at ‘ Read Job ‘, select ‘ Run Now ‘ action. This connector enables you to: Create, update, and delete entities. When you create a new MDF generic object (GO), you can choose whether you want to expose it to OData API. Okta’s pre-built integration with SuccessFactors brings HR and IT systems together, letting user data and profile updates in SuccessFactors inform the. 0 : The Security Assertion Markup Language (SAML) version 2. Properties and Navigation Properties. Now customers can use new SCIM APIs (not OData) with a certificate-based approach. (Optional) Check whether your access token has expired or not. This KBA provides information about Successfactors Odata API Recommended Usage and Best Practices SAP Knowledge Base Article - Preview 2735876 - Odata API Best Practices [Query Modified Records, Pagination - Batch Size, Timeouts, etc. To find right OData end point URL for your SuccessFactors instance refer this link. svc. ICF inturn invokes a search operation on the SuccessFactors Connector Bundle and then the bundle calls the OData API for reconciliation operation. SAP SuccessFactors offers a comprehensive set of Role Based Permission (RBP) APIs based on OData V2. These support cases should be handled over to LOD-SF-INT-OUT component. OAuth Client Registration. In SuccessFactors, navigate to SuccessFactors > Admin Center > Company Settings > Manage OAuth2 Client Applications > Register Client Application. SuccessFactors OData API query, Historical records missing in the response, Employee Central (EC) effective dated entities behavior, toDate, fromDate, Latest record , KBA , LOD-SF-INT , Integrations , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT-API , API & Adhoc API Framework , LOD-SF-INT-EC , Employee Central. S – In the below output JSON code, i’ve shown only 3 types. In Azure, modify one existing user's attribute (for example user. Boghyon Hoffmann. Different touch points for API:Click Here to access the SuccessFactors OData API Developer Guide Keywords OData, Developer, Guide, API, Data, Dictionary, O, Entity , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-RCM-API , Webservices & APIs , How ToThis guide focuses on OData version 2. You can use the dictionary to look up EntitySets, Complex Types, and Function Imports that are. It really depends on the server side implementation, and SuccessFactors actually supports it. select Services > Service Marketplace, and on the right-side search for SAP SuccessFactors Extensibility and select it; Click on Create in the next window and add the following settings Service: SAP SuccessFactors Extensibility. Using the search filters Entity, Complex Type, or Function Import also lets you narrow your search by Tag, for example EC - Payment Information . Available SFSF API test system. 1. Integration center; Cause. You can use this entity to query and edit the information of legacy. The SAP SuccessFactors HXM Suite OData API is a Web Service API feature based on the OData protocol. DateTimeOffset data types of the OData protocol. Note If you want to create an onboarding external user record in the system with the information collected from your external ATS, it is recommended that you use the createOnboardee API instead of using the ExternalUser API. First, it's worth noting that the SuccessFactors API will paginate result sets when more than 1000 entities are returned. It is able to trace changed records by filtering last modify date. A platform for all people and HR data that transforms your work experience. The API key generated will be needed in the next step. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. You can use below references to know more about SFSF Adapter and Query Modeler. Tenant URL – Enter the name of the SuccessFactors OData API services endpoint. Leveraging the Destination Service x. Use Case 1: Get Email Addresses by Specific Criteria. The SAP SuccessFactors Human Experience Management (HXM) Suite supports extensibility and integration with third-party solutions using comprehensive application programming interfaces (APIs). SAP Online HelpIn this example, the user logs in to a sender app to fetch tasks retrieved from an SAP SuccessFactors system (which, in OAuth terms, contains the protected resources). Postman is used to call the iflow URL (1), the request message body (2) is ignored in my demo. This issue can happen with any Odata entity in SuccessFactors and this blog will help to understand why it happens and how to get rid of it. Use search and filter to find the corresponding servers for your company. successfactors. There is a entity so heavy that the default 1000 records return per request always causes server to timeout. Step a: Add a Request-Reply step to make OData call to get User data from SuccessFactors with below configuration. The CompoundEmployee application programming interface (API) for SAP SuccessFactors Employee Central is used to extract employee data out of Employee Central. Wait until you see a success message, along with a date and timestamp. The SAP SuccessFactors HXM Suite OData API is a Web Service API feature based on the OData protocol. This PerEmail API enables you to read, update, create, or delete an employee's email address. In the upcoming releases, we will be supporting some more features and blog for the same will be updated. This is even more true for integrations and API based communication. Using postman everything works fine but, once I check the connection of destination previously created, the response received is 401: Unauthorized. 2613670 – What are the available APIs for SuccessFactors? You can also check the SF available Fields in the API Center with in SuccessFactors. With enhanced SAP SuccessFactors oData V2 outound connector, it’s possible to configure oAuth SAML Bearer in context of an API user for SAP SuccessFactors system.