Skip to main content
Question

How to call an IFS projection with the REST API task in Workflow?

  • September 12, 2025
  • 4 replies
  • 151 views

Forum|alt.badge.img+1

Hi Community,

 

Can you please advise on how to call a same instance IFS projection which I can’t get access to with the IFS API Task?

Do I have to set up an IAM client to do so? Or is there a built-in token within the Workflow or something like that?

Thank you so much.

Marcos

4 replies

PhillBronson
Hero (Customer)
Forum|alt.badge.img+11
  • Hero (Customer)
  • September 12, 2025

Do you have details on the projection and call you’re trying?


Forum|alt.badge.img+1
  • Author
  • Do Gooder (Employee)
  • September 12, 2025

Hey Phill,

 

I want to add new entities to AddressTypes using the ForwarderHandling projection.

I’ve managed to create a new forwarder and its addresses using the IFS API task, but the address types seem to be “nested” under the nested entity ForwarderInfoAddresses, so I couldn’t find a way to get to it.

Here’s the endpoint:

/main/ifsapplications/projection/v1/ForwarderHandling.svc/ForwarderInfoSet(ForwarderId='{ForwarderId}')/ForwarderInfoAddresses(ForwarderId='{ForwarderInfoAddress_ForwarderId}',AddressId='{ForwarderInfoAddress_AddressId}')/AddressTypes

 

Thanks


Forum|alt.badge.img+3
  • Do Gooder (Employee)
  • September 15, 2025

Hi @nobmus 

What is the track you are using?

From 24R2 onwards, authentication is available directly inside the REST Task. You can check the documentation here:
Authentication – REST Call Task

Thanks


Forum|alt.badge.img+1
  • Do Gooder (Customer)
  • June 18, 2026

Is there any solution for 24r1? I’ve tried getting the Bearer tokens using an IAM Client but even though it works using Postman, the exact same API call to get the token fails in Workflow (along with other identical API calls to retrieve information). Other (external) API’s that I’ve tested have worked perfectly fine in Workflow however.