API Calls Breaking After Upgrading from V6 to V8?

Toa_Lihkan

Greetings,

A fellow of mine also using Decisions is having some API issues after upgrading from Decisions v6 to v8. He's making a POST call to the flow somewhat resembling http://{hisbaseportalurl}/Primary/restapi/Flow/{hisflowid}?sessionid={his session ID}

He hasn't updated any of the query parameters in the flow, but this call seems to be failing after the upgrade. Any idea what could be causing this?

gregory_Decisions

Hello!

Without seeing the error you are getting, we cannot say for certain the cause. However, it does look like the issue might be the way you are calling the API. In V6, you could call Decisions Flows with query parameters in the URL. In v8, Flows are called as APIs via Path Parameters. https://documentation.decisions.com/v8/docs/api-and-authentication

Navigate to the Flow you are trying to call via API and go into the flow editor. From there, select "Configure Integration" and choose API Service:

Afterwards, click View. This should open a separate window that displays the integration details. Select the Setup and click the Test tab to view the proper URL to call and what parameters to pass into the body of your POST call:

We hope this helps!

-Gregory