API Flow: Resolving Error 412 in ION Messaging Integration

Marlene Gräfe · 2025-04-07T07:42:57+00:00

There was an error rendering this rich post.

Hello,

I have an issue with my API flow and need assistance. In my use case, I have:

A workflow that is triggered by a schedule and calls an API flow.
The API flow that runs several API calls and should send a message via IONSERVICES/api/ion/messaging/service/v2/message at the end.
A document flow that is triggered by the IMS message.

I successfully tested the document flow using Postman and the workflow. However, the API flow only works up to the IMS messaging call, which consistently fails with error 412 "Invalid client ID provided," despite using the same credentials as the Postman test (see image bottom request).

It appears that this API endpoint cannot be called in any flow. I have also tested it with a service account that has all authorization scopes, but there was no change.

Is it generally possible to use this endpoint within ION flows, or is it only defined for external applications?

If it is generally usable, what could be causing the 412 error? Is there a way to view the credentials (Bearer token) used for this call? In API Gateway Monitoring, I only see the service account used.

Thank you for your help.

Best regards,
Marlene

Find more posts tagged with

Accepted answers

All comments

Marlene Gräfe

Sorry for editing my post so much, but I needed to change the image. And there was no visible feedback, that changes will be approved. I only saw it now in the browser console.

Marlene Gräfe

It looks like the updates of my post didn't work well. Then as additional information in the comment:

I successfully tested the workflow and the document flow using Postman. However, the API flow only works up to the IMS messaging call, which consistently fails with error 412 "Invalid client ID provided," despite using the same credentials as the Postman test.
Both requests showed in API Gateway monitoring the same service account.

It appears that this API endpoint cannot be called in any flow type. I have also tested it with a service account that has all authorization scopes, but there was no change.

Carsten Steinhoefel

The problem is that you have to pass the correct Client ID that is defined in the IMS Connection Point when authenticating. The API flow (or workflow) have their own Client ID and don't let you provide one.

This is the same reason that you cannot run the IMS API in the Documentation page in the API Gateway.

Jonas Nielsen

You need to find the correct ION Client Id.
In "API Gateway" go to "Authorized Apps". In this list find the one called "IONWorkflow-{tenantID}_{TenantType} eg. IONWorkflow-MYTENANT_TRN.

Take the Client Id from that and use that in the IMS Connection Point.
No need to create credentials or anything in the authorized app.

Marlene Gräfe

Thank you! That was the solution. I used the wrong Client Id.