Using REST Sender to POST a new resource to a destination system, the destination correctly returns HTTP 201 (Created), but IFS flags this as an error rather than a success — IFS appears to only treat HTTP 200 as a success code by default. Is there a way to make IFS also accept 201, or other non-200 success codes, as valid?

All FAQ questions / Integrations and APIs

Answer

Yes — by default REST Sender only treats HTTP 200 as a successful response, but this is configurable: specify the additional HTTP status codes you want treated as successful, like 201, directly in the REST Sender's own configuration, rather than only 200 being accepted. Once configured, responses with those additional accepted codes are correctly treated as successful rather than flagged as errors.

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