On IFS9, without a native REST destination type, an outbound HTTP Routing Address POSTing to a known third-party API returns 'Internal server error,' even though the headers and message body have been confirmed correct against the same endpoint using a REST testing tool.

All FAQ questions / Integrations and APIs

Answer

Check whether the target API only correctly processes a request containing a single, correctly-formed Content-Type header value — many HTTP endpoints only honor the first Content-Type header they receive and mishandle or reject anything else, including a request that ends up with more than one Content-Type value or one that doesn't match what the endpoint expects (for example application/json specifically). Confirm the routing address configuration sends exactly one correct Content-Type header value matching what the target API actually requires, rather than assuming the headers are fine just because they looked correct when captured from a working REST-tool request.

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