Skip to main content
Solved

24r1 Workflow IFS internal REST API Call

  • June 18, 2026
  • 2 replies
  • 32 views

Forum|alt.badge.img+2

When attempting to use the IFS REST API Task in Workflow, internal API calls always result in a 500 response error. This doesn’t occur when other, external APIs are called the same way (like https://postman-echo.com/post) which run as expected. 

Calling internal APIs always returns the same 500 error. The APIs worked when called through Postman, however when using the Workflow and attempting to replicate the API request, it fails.

For example, here’s the api request I use to get the a Bearer token which fails in IFS Workflow but succeeds in postman:
 

 

Best answer by dominikdurrer

@ext.nchen2 trying a similar internal call in 25R2 with the same error.

A workflow worked perfectly until code changes by IFS, and now its no longer supported: https://docs.ifs.com/techdocs/25r2/040_tailoring/500_business_process_automation/025_considerations/020_ifs_api_task_considerations/#unsupported_apis

Kind of a bummer as this potentially renders workflows somewhat useless

2 replies

Forum|alt.badge.img+9
  • Hero (Customer)
  • Answer
  • June 22, 2026

@ext.nchen2 trying a similar internal call in 25R2 with the same error.

A workflow worked perfectly until code changes by IFS, and now its no longer supported: https://docs.ifs.com/techdocs/25r2/040_tailoring/500_business_process_automation/025_considerations/020_ifs_api_task_considerations/#unsupported_apis

Kind of a bummer as this potentially renders workflows somewhat useless


Forum|alt.badge.img+2
  • Author
  • Do Gooder (Customer)
  • June 22, 2026

Thanks for the response. I’ve also tried manually calling the api’s using the IFS REST API Task and IAM Clients instead of the regular IFS API task. However, although the process works when tested in postman, trying to call internal APIs using the IFS REST API Task results in a 500 or 503 error. Do you know why this may be?