These fields are used when a third party application uses a different message protocol than OData (REST/SOAP etc.). 

https://docs.thinkwisesoftware.com/docs/sf/process_flows.html#a-message-protocol-independent-web-service-in-a-process-flow

Hello K.Bakkenes,

The API and API alias fields are currently ignored by Indicium. Given the names of these fields, I understand your assumption that you would need to use these if you want to start your process flow with an API call, but this is not the case.

Every process flow can be started with an API call.

But if you want to keep it simple, please make sure that your process flow follows these requirements:

• Have only one starting action (only one arrow leaving the Start process action).
• Use only system flow actions (this excludes tasks and reports as well).

If you stick to those requirements, starting your flow is as simple as the following API call:

POST
/iam/appl/process_flow_id

If the first process action in your flow is a task, an add record, an edit record or a delete record action, then you can start your process flow by performing the corresponding API call. It will trigger the flow automatically. In this case it doesn't matter if you have multiple starting actions, but please make sure that the rest of your process actions are system flow actions.

I hope this helps.

Hello Erwin and Vincent,

thank you for your responses. The purpose of these API setting fields is clear now.