Skip to Content

SuccessFactors OData API Test system


For those  looking for publicly available SuccessFactors system  to create  extension application  on SAP Cloud Platform trial account, then you must read this blog which  will guide you through detailed steps to access test SuccessFactors system. OData API test SuccessFactors system exposes SuccessFactors OData service  to create  extension applications  on SAP Cloud Platform trial account to jump start  learning journey of SuccessFactors extensions.

SuccessFactors OData API test system

Click on above link and go to section:- “SuccessFactors OData API Test system

The  SuccessFactors OData API test system comes with a predefined set of users and data configured in READ ONLY mode.  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.

Available SFSF API test system users: mbarista1 and nnnn.

You can access the test system using the following URL

That is the Root URL to OData API and it returns ServerErrorException. You need to make some valid OData query like‘bmays1’) to get some response. The authentication method is BASIC and you should use your SAP Cloud Platform trial user and password to authenticate. For demo purposes, the request to the test system may contain an X-Proxy-User-Mapping header in the <user|SFSF_user> format. This header allows you to map a user to one of the following SFSF API test system users: mbarista1 and nnnn.
For example, if you execute the following request:‘i123456’) with header: X-Proxy-User-Mapping: i123456|nnnn the response will contain results for the nnnn SFSF API test system user.

where  i123456 is your SAP Cloud Platform trial user.

Try below URL to get user details like first name, last name ,email,  date of the birth for a given user.$select=userId,firstName,lastName,email,dateOfBirth&$filter=userId eq ‘nnnn’

when prompted for user id and pwd, enter your  SAP Cloud Platform trial account user id and password.


You can also define destination on SAP Cloud Platform to consume OData service from  above test system via WEB IDE “HTML5” or Java application.

Define destination with following parameters

Destination Name sap_hcmcloud_core_odata
Description SuccessFactors Test PROXY  OData API System
Type http
Proxy Internet
Authentication BasicAuthentication
User  i123456
Password <pwd>

where user and password are  user credentials of your SAP Cloud Trial  Account.

Additional Properties:-

TrustAll True
WebIDEEnabled True
WebIDEUsage odata_gen

Note:-  The above system is only good for   accessing OData API’s to create some UX extensions on SAP Cloud Platform trial account for learning purposes, you will not have any access to SucccessFactors  system.

You must be Logged on to comment or reply to a post.
  • Hi there,

    I' m really interrested to this this interface, but it looks like your credentials are not working anymore, is this possible?




    • The destination dont works for me NOW...Can you help? What we can do to test extend apps now?

      Description=SuccessFactors PROXY Core OData API
      User=<Your s/p/i/d username>
      Password=<Your s/p/i/d password>

  • Hello ,

    i made a destination from HCP to Successfactors and the destination is working fine , also i created an app that will call successfactors odata so i consumed my destination , every thing goes fine but i need to have the logged in user in successfactors once i opened my application so i can use it in the rest of the odata calls  , how to retrieve that data ?

    here is my code

    ctx = new InitialContext();
    ConnectivityConfiguration configuration = (ConnectivityConfiguration) ctx.lookup("java:comp/env/connectivityConfiguration");

    DestinationConfiguration destConfiguration = configuration.getConfiguration("SuccessFactors");
    String value = destConfiguration.getProperty("URL");

  • Hello Manju,


    Is this system still available? No matter how I try it (browser, postman or in SCP) I will always get a 500 error.

    Thanks for the information!