25r2 Workflow IFS internal REST API Call

​@ext.nchen2  could we have more contexte please?

Which API are you trying to call? whata parameters?...Etc

​@N.GEORGI  

Thanks for the response, I am trying to access this API: 
GET /main/ifsapplications/projection/v1/SupplierHandling.svc/SupplierInfoGeneralSet(SupplierId='XXXXXX')/SupplierPayments(Company='XXXXX',Identity='XXXXX',PartyType=IfsApp.SupplierHandling.PartyType'Supplier')/PaymentWayArray

 
The request works in postman with an Authorization token, but no method seems to work in workflow (there is no body in the request)
 

Hi ​@ext.nchen2 

I tried calling the API you mentioned using a REST task with both the same host and a different host in the 25R2 central environment. Here are the workflow steps I followed. I hope this is similar to what you are trying to do as well.

Same Host (ifs25r2bnddevcmb)

Different Host (calling an API hosted in ifs25r2bnddevlkp from ifs25r2bnddevcmb)

1. Create a REST Task Configuration. The IAM details can be found on the IAM Client page in ifs25r2bnddevlkp .

   

    

   Token Endpoint : https://ifs25r2bnddevlkp.rnd.ifsdevworld.com/auth/realms/ifs25r2bnddevlkp/protocol/openid-connect/token
   
    

2. Select Authentication Type as OAuth 2.0 and set Auth Config Name to the REST Task Configuration you created.

   

    

​@pdollk Thanks for the response, I’ve tried the exact same setup with both no authentication and the OAuth 2.0, both on the same realm. However I run into errors.

 

Hi ​@ext.nchen2 , 

If i were to suggest an alternative approach to try out and see

We may be able to take advantage of how the OData spec works here for our advantage.

In “API explore,” page we can analyze how the api spec is declared. The request format appears as shown below. Under “SupplierHandling,” in the “Get entities from PaymentWayArray” section, the GET request is:

/main/ifsapplications/projection/v1/SupplierHandling.svc/SupplierInfoGeneralSet(SupplierId='{SupplierId}')/SupplierPayments(Company='{IdentityPayInfo_Company}',Identity='{IdentityPayInfo_Identity}',PartyType=IfsApp.SupplierHandling.PartyType'{IdentityPayInfo_PartyType}')/PaymentWayArray

the actual request you shared is like this

GET /main/ifsapplications/projection/v1/SupplierHandling.svc/SupplierInfoGeneralSet(SupplierId='XXXXXX')/SupplierPayments(Company='XXXXX',Identity='XXXXX',PartyType=IfsApp.SupplierHandling.PartyType'Supplier')/PaymentWayArray

From there, we should be able to reference SupplierPayments directly, which is really an IdentityPayInfo entity reference underneath. Per the OData spec, we can point to it through Reference_IdentityPayInfo and then use the “PaymentWayArray” nested entity array to pull the information needed in the API task below.

for the Party type we have the following options, in this case its “Supplier”

in the API task we can do a call like this get the same result 

​@kamnlk Thanks a lot for your response. Although this method does work, the reason I wanted to access that specific API was so that I could update, modify, and delete the entries within it. Do you know any way to do this or how to fix my original problem of the IFS REST API always having a 500 http error for only IFS API calls (including other realms)?