A client-credentials token request seems to send the client ID and secret in two different places in the same request (both as Basic Authentication and elsewhere), causing problems for some receivers.

All FAQ questions / Integrations and APIs

Answer

Check for a known, since-fixed defect in how client credentials were sent in the token request before working around it on the receiving end — this has been a confirmed platform issue with a patch introducing an explicit property to control that behavior, so check your patch level rather than building a permanent workaround for it.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions